Current status:
Steering Committee (SC)-related documentation is scattered across different sections of the governance documentation.
Recommendations:
-
It would be best to consolidate SC-related documentations for readability.
-
Explicitly creating a charter for the SC (much of the content needed is already documented or in issues). This charter should include:
- Mission
- Direct responsibilities
- Membership
- Decision making/voting
- Members removal/emeritus (separate processes for intentional step-down/reafirm affiliation as well as removals, for example “no confidence” or similar)
-
Additional docs worth adding:
Additionally, the matter of access/GitHub privileges for emeritus members should be resolved (right now emeritus members inherit from the SC in GH and thus retain elevated access to the GitHub organisation, leading to potential security risks).
References:
Current status:
Steering Committee (SC)-related documentation is scattered across different sections of the governance documentation.
Recommendations:
It would be best to consolidate SC-related documentations for readability.
Explicitly creating a charter for the SC (much of the content needed is already documented or in issues). This charter should include:
Additional docs worth adding:
Additionally, the matter of access/GitHub privileges for emeritus members should be resolved (right now emeritus members inherit from the SC in GH and thus retain elevated access to the GitHub organisation, leading to potential security risks).
References: