This document outlines the recommendations and requirements for defining SIG and subproject governance.
This doc uses rfc2119 to indicate keyword requirement levels. Sub elements of a list inherit the requirements of the parent by default unless overridden.
Following is the checklist of items that should be considered as part of defining governance for any subarea of the Kubernetes project.
MUST define when and how collaboration between members of the SIG is organized
MAY define process for new community members to contribute to the area
MUST define how subprojects are managed
The following checklist applies to both SIGs and subprojects of SIGs as appropriate:
MUST define how milestones / releases are set
SHOULD define how priorities / commitments are managed
All technical assets MUST be owned by exactly 1 SIG subproject. The following checklist applies to subprojects:
MUST define how technical decisions are communicated and made within the SIG or project
MUST define how technical assets of project remain healthy and can be released