Yea, there are a lot of possibilities for things the team can do, and I'm interested in everyone's ideas. But at least step #1 is getting the meetings going again and some basic organization of ideas, tasks, etc. That's what I'm going to be focusing on this next week or so. From there I'm up for any any all help and ideas from everyone.
On Mon, May 9, 2022 at 9:08 AM Major Hayden major@mhtx.net wrote:
On Mon, May 9, 2022, at 08:00, JT wrote:
Since Fedora mostly consumes upstream projects most of the active security work will be upstream in the respective projects, but there's still work to be done at the Fedora level. Of which I see four primary areas: A) Monitoring things that are reported to the team. B) Reporting and working upstream on any reports/issues that come in C) Managing Community questions about security issues D) Shepherding of long term project with security impacts
I'm glad to help with all of these, especially C. There's also a good opportunity for us to be proactive around security with blog posts (Fedora Magazine, maybe?) and/or updates to Fedora documentation.
-- Major Hayden _______________________________________________ security mailing list -- security@lists.fedoraproject.org To unsubscribe send an email to security-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/security@lists.fedoraproject.o... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure