Formalize Security Team as owning SIG/Security, and discuss FIPS contribution to Rocky via this SIG #2

New Issue

neil · 2023-08-16T21:20:14Z

neil commented

2023-08-16 21:20:14 +00:00

No description provided.

neil added the

Meeting

label 2023-08-16 21:20:21 +00:00

neil commented

2023-08-27 18:47:36 +00:00

from memory (tab with my draft got lost :\ ):

No one was opposed to this overall
We need to deliniate between a Team and a SIG -- teams and members can belong to SIGs, but are sometimes disjoint from them. e.g., Security Team may be responsible or have a say in the Security SIG, but the SIG is more about packaging and/or "consumables", whereas the Team is more focused on the organization and its goals which may or may not be consumables (or public)

@brian did I miss anything that you remember? Or anyone else?

Action items:

Create an actual security SIG group, and assign permissions
- Make Scott and Rob the sponsors of the SIG to start out with
Define what a Team is, what a SIG is.. What does the structure of the RL Project actually look like now?

from memory (tab with my draft got lost :\ ): * No one was opposed to this overall * We need to deliniate between a Team and a SIG -- teams and members can belong to SIGs, but are sometimes disjoint from them. e.g., Security Team may be responsible or have a say in the Security SIG, but the SIG is more about packaging and/or "consumables", whereas the Team is more focused on the organization and its goals which may or may not be consumables (or public) @brian did I miss anything that you remember? Or anyone else? Action items: * Create an actual security SIG group, and assign permissions * Make Scott and Rob the sponsors of the SIG to start out with * Define what a Team is, what a SIG is.. What does the structure of the RL Project actually look like now?

Sign in to join this conversation.