SIG Charter Guide
All Kubernetes SIGs must define a charter defining the scope and governance of the SIG.
- The scope must define what areas the SIG is responsible for directing and maintaining.
- The governance must outline the responsibilities within the SIG as well as the roles
owning those responsibilities.
Steps to create a SIG charter
- Copy the template into a new file under community/sig-YOURSIG/charter.md (sig-architecture example)
- Read the Recommendations and requirements so you have context for the template
- Fill out the template for your SIG
- Update sigs.yaml with the individuals holding the roles as defined in the template.
- Add subprojects owned by your SIG in the sigs.yaml
- Create a pull request with a draft of your charter.md and sigs.yaml changes. Communicate it within your SIG
and get feedback as needed.
- Send the SIG Charter out for review to firstname.lastname@example.org. Include the subject “SIG Charter Proposal: YOURSIG”
and a link to the PR in the body.
- Typically expect feedback within a week of sending your draft. Expect longer time if it falls over an
event such as Kubecon or holidays. Make any necessary changes.
- Once accepted, the steering committee will ratify the PR by merging it.
Steps to update an existing SIG charter
- For significant changes, or any changes that could impact other SIGs, such as the scope, create a
PR and send it to the steering committee for review with the subject: “SIG Charter Update: YOURSIG”
- For minor updates to that only impact issues or areas within the scope of the SIG the SIG Chairs should
facilitate the change.
How to use the templates
SIGs should use the template as a starting point. This document links to the recommended SIG Governance but SIGs may optionally record deviations from these defaults in their charter.
The primary goal of the charters is to define the scope of the SIG within Kubernetes and how the SIG leaders exercise ownership of these areas by taking care of their responsibilities. A majority of the effort should be spent on these concerns.
See frequently asked questions