diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-04-09 11:37:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-09 11:37:09 -0700 |
| commit | 7f4500e1bdbee51b60cafcff38c7c24ffbd75bb8 (patch) | |
| tree | b56c9f48c32cdd252e11eb4ec41666719b4f7181 | |
| parent | c5173d55923e875e089348f63f59d721b4e3f7ec (diff) | |
| parent | e69abdf8ab4dccf3e80ac07ab30483ca7155c218 (diff) | |
Merge pull request #2021 from castrojo/add-lead-list
Add sig lead list reference, update slack admin information
| -rw-r--r-- | sig-governance.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/sig-governance.md b/sig-governance.md index dd28d606..f2e0e3e5 100644 --- a/sig-governance.md +++ b/sig-governance.md @@ -24,7 +24,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare * Propose the new SIG publicly, including a brief mission statement, by emailing kubernetes-dev@googlegroups.com and kubernetes-users@googlegroups.com, then wait a couple of days for feedback * Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo -* 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 the #slack-admins channel. 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` * 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 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. @@ -37,6 +37,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare 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 +* Leads should [subcribe to the kubernetes-sig-leads mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-leads) * 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. ### **Creating service accounts for the SIG** |