diff options
| -rw-r--r-- | sig-governance.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sig-governance.md b/sig-governance.md index e844608b..e9d50039 100644 --- a/sig-governance.md +++ b/sig-governance.md @@ -34,7 +34,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare 2. Share it with all SIG leads with full ownership of the calendar - they can edit, rename, or even delete it. 3. Share it with `sc1@kubernetes.io`, `sc2@kubernetes.io`, `sc3@kubernetes.io`, with full ownership. This is just in case SIG leads ever disappear. 4. Share it with the SIG mailing list, lowest priviledges. - 5. Share it with `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com` to publish on the universal calendar. + 5. Share individual events with `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com` to publish on the universal calendar. * Use existing proposal and PR process (to be documented) * Announce new SIG on kubernetes-dev@googlegroups.com * Submit a PR to add a row for the SIG to the table in the kubernetes/community README.md file, to create a kubernetes/community directory, and to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory. |