The SIG Council exists to manage investigations of technical issues among the SIGs and coordinate requests to the CentOS Stream and CentOS Infrastructure teams.
Membership is made up of the SIG Chair (or their designee) from each Active SIG as determined by the board. Standing invites to the meeting are given to members of the CentOS Infrastructure Team at Red Hat, a representative from the CentOS Stream Engineering team, and a representative from RHEL Engineering. The SIG may request attendance at certain meetings from other stakeholders through the Board or the Red Hat Liason.
The Board will determine future governance, but the initial requirements are: - Regular, minuted meetings - A strong preference for deliberative, open, discussion - The ability to enter Executive session to discuss sensitive technical matters. To be used only in extraordinary circumstances
The board also requests this group produce a State of the SIGs report on a regular basis.
Minor edit: s/The Board will determine future governance/The SIG Council will determine future governance, in accordance with the principles set forward by the Board/ -- mostly to make it explicit the Council doesn't need to involve the Board when making routine governance decisions (say, when to schedule meetings and stuff like that). lgtm otherwise, thanks for putting this together!
Following on Davide's comment, I think if a large change like instituting voting in the future is being discussed it should include the Board. That said I think our input might be advisory on wording, etc similar to the role we played in Brussels that got us to this revised version.
I would however like to see the regular basis defined similar to how we've been doing that for SiG and Board activity so that it's measurable. Whether it's quarterly or twice yearly I think it can be discussed by the group and then added to the Governance. I do think yearly might be too long though.
Login to comment on this ticket.