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

Make contact information for calendars more explicit

This commit is contained in:
Jorge O. Castro 2017-10-18 13:36:14 -04:00
parent 04377a1b80
commit 7a0c8fdec0
1 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
sig-governance.md
View File

@ -27,18 +27,14 @@ In order to standardize Special Interest Group efforts, create maximum transpare
* Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). New users can join at [slack.kubernetes.io](http://slack.kubernetes.io). * Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). New users can join at [slack.kubernetes.io](http://slack.kubernetes.io).
* Slack activity is archived at [kubernetes.slackarchive.io](http://kubernetes.slackarchive.io). To start archiving a new channel invite the slackarchive bot to the channel via `/invite @slackarchive` * Slack activity is archived at [kubernetes.slackarchive.io](http://kubernetes.slackarchive.io). To start archiving a new channel invite the slackarchive bot to the channel via `/invite @slackarchive`
* Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there. * Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there.
* Request a Zoom account from from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. * Request a Zoom account by emailing Paris Pittman(`parispittman@google.com`) and Jorge Castro(`jorge@heptio.com`). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary.
* Read [how to use YouTube](https://github.com/kubernetes/community/blob/master/community/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel. * Read [how to use YouTube](https://github.com/kubernetes/community/blob/master/community/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel.
* Calendars * Calendars
1. Create a calendar on your own account. Make it public. 1. Create a calendar on your own account. Make it public.
2. Share it with all SIG leads with full ownership of the calendar - 2. Share it with all SIG leads with full ownership of the calendar - they can edit, rename, or even delete it.
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.
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. 4. Share it with the SIG mailing list, lowest priviledges.
5. Share it with `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com` 5. Share it with `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com` to publish on the universal calendar.
to publish on the universal calendar.
* Use existing proposal and PR process (to be documented) * Use existing proposal and PR process (to be documented)
* Announce new SIG on kubernetes-dev@googlegroups.com * 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. * 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.