diff options
| author | eduartua <eduartua@gmail.com> | 2018-10-25 20:06:31 -0500 |
|---|---|---|
| committer | eduartua <eduartua@gmail.com> | 2018-10-25 20:26:19 -0500 |
| commit | c3deebee32ed017bad0b9ed4fd5e1cad31d52db8 (patch) | |
| tree | 312e536f30521b903550515627b60df516b0798e /committee-steering | |
| parent | 333df5cf3c868055484f32eabee08bf741a363aa (diff) | |
Conformance of the names of the conferences file: community/committee-steering/governance/README.md
Diffstat (limited to 'committee-steering')
| -rw-r--r-- | committee-steering/governance/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index b61ac493..b99d0d6c 100644 --- a/committee-steering/governance/README.md +++ b/committee-steering/governance/README.md @@ -18,7 +18,7 @@ All Kubernetes SIGs must define a charter defining the scope and governance of t 6. 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. 7. 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. + event such as KubeCon/CloudNativeCon or holidays. Make any necessary changes. 8. Once accepted, the steering committee will ratify the PR by merging it. ## Steps to update an existing SIG charter |