kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6272 from goern/goern-patch-1 

committee-steering/governance/README.md: Typo fixes
This commit is contained in:
Kubernetes Prow Robot 2021-12-09 23:49:20 -08:00 committed by GitHub
parent d40d84101d 6e5a5aa84a
commit 70eb08d97a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
committee-steering/governance/README.md
View File

@ -13,13 +13,13 @@ All Kubernetes SIGs must define a charter defining the scope and governance of t
3. Fill out the template for your SIG 3. Fill out the template for your SIG
4. Update [sigs.yaml] with the individuals holding the roles as defined in the template. 4. Update [sigs.yaml] with the individuals holding the roles as defined in the template.
5. Add subprojects owned by your SIG in the [sigs.yaml] 5. Add subprojects owned by your SIG in the [sigs.yaml]
5. Create a pull request with a draft of your charter.md and sigs.yaml changes. Communicate it within your SIG 6. 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. and get feedback as needed.
6. Send the SIG Charter out for review to steering@kubernetes.io. Include the subject "SIG Charter Proposal: YOURSIG" 7. Send the SIG Charter out for review to steering@kubernetes.io. Include the subject "SIG Charter Proposal: YOURSIG"
and a link to the PR in the body. and a link to the PR in the body.
7. Typically expect feedback within a week of sending your draft. Expect longer time if it falls over an 8. Typically expect feedback within a week of sending your draft. Expect longer time if it falls over an
event such as KubeCon/CloudNativeCon or holidays. Make any necessary changes. event such as KubeCon/CloudNativeCon or holidays. Make any necessary changes.
8. Once accepted, the steering committee will ratify the PR by merging it. 9. Once accepted, the steering committee will ratify the PR by merging it.
## Steps to update an existing SIG charter ## Steps to update an existing SIG charter