#meeting-3:fedoraproject.org: security-sig

Meeting summary

1. LINK: Issue Location : https://forge.fedoraproject.org/security/tickets (@q5sys:matrix.org, 15:01:08)
2. LINK: Discourse security tagged topics :https://discussion.fedoraproject.org/tag/security (@q5sys:matrix.org, 15:01:13)
3. TOPIC:Open floor to discuss anything security related. (2026-07-02) (@q5sys:matrix.org, 15:01:17)
4. TOPIC:Next Meeting (2026-07-09) (@q5sys:matrix.org, 15:01:19)
1. INFO: There are 7 open tickets in the main Security Forge: https://forge.fedoraproject.org/security/tickets/issues (@q5sys:matrix.org, 15:01:21)
2. INFO: There are 6 open tickets in the Security Docs Forge: https://forge.fedoraproject.org/security/docs/issues (@q5sys:matrix.org, 15:01:23)
3. INFO: Agenda: https://discussion.fedoraproject.org/t/security-sig-meeting-agenda-for-the-meeting-on-02-07-2026/195393/1 (@q5sys:matrix.org, 15:01:46)
5. TOPIC:Introduce a quorum to mitigate unnecessary meetings and use "meeting" label (@decathorpe:fedora.im, 15:03:31)
6. TOPIC:Introductions (@decathorpe:fedora.im, 15:10:14)
1. AGREED: Agenda for upcoming meetings will be published in advance. Formal decisions require votes from at least three SIG members. (+4, 0, -0) (@decathorpe:fedora.im, 15:43:39)
7. TOPIC:Shall the Security Docs in the Security SIG’s repo consolidate all security topics in general (and maybe also integrate other Security Docs still in Quick Docs or so), or only contain Docs that are jointly/reliably maintained by the Security SIG? (@py0xc3:fedora.im, 15:47:34)

Action items

1. (none)

People present (lines said)

1. @decathorpe:fedora.im (55)
2. @py0xc3:fedora.im (48)
3. @q5sys:matrix.org (26)
4. @ljavorsk:fedora.im (17)
5. @rzhukov:matrix.org (16)
6. @salimma:fedora.im (15)
7. @meetbot:fedora.im (3)
8. @zodbot:fedora.im (3)
9. @mfindra:matrix.org (3)
10. @jforbes:fedora.im (2)