Update sig-creation-procedure.md

1 files changed, 14 insertions, 9 deletions

diff --git a/sig-creation-procedure.md b/sig-creation-procedure.md
index cb597285..1231ba94 100644
--- a/sig-creation-procedure.md
+++ b/sig-creation-procedure.md
@@ -1,30 +1,30 @@
 ### SIG creation procedure
 
 * 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
-* Create a group (see the detailed instructions below)
 * Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo
-* If you wish, request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from @sarahnovotny.  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 @sarahnovotny.  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 from @sarahnovotny if you expect more than 30 attendees or attendees from China.
  * Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com.
-* Use existing proposal and PR process
-* Announce new SIG on kubernetes-dev@googlegroups.com and ask a repo maintainer to create a kubernetes/community directory and github team for the new group
-* Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory.
-* 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`
+* 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.
 
 #### 
 **Google Groups creation**
 
 Create Google Groups at [https://groups.google.com/forum/#!creategroup](https://groups.google.com/forum/#!creategroup), following the procedure: 
 
-* Create a group using the name convention below;
-* Group has to be created as an e-mail list with at least three owners (including sarahnovotny at google.com and ihor.dvoretskyi at gmail.com);
+* Each SIG should have one discussion groups, and a number of groups for mirroring relevant github notificaitons;
+* Create groups using the name conventions below;
+* Groups should be created as e-mail lists with at least three owners (including sarahnovotny at google.com and ihor.dvoretskyi at gmail.com);
 * To add the owners, visit the Group Settings (drop-down menu on the right side), select Direct Add Members on the left side and add Sarah and Ihor via email address (with a suitable welcome message); in Members/All Members select Ihor and Sarah and assign to an "owner role";
 * Set "View topics", "Post", "Join the Group" permissions to be "Public"
 
-
 Name convention:
 
+* kubernetes-sig-foo (the discussion group)
 * kubernetes-sig-foo-misc
 * kubernetes-sig-foo-test-failures
 * kubernetes-sig-foo-bugs
@@ -35,6 +35,7 @@ Name convention:
 
 Example:
 
+* kubernetes-sig-onprem
 * kubernetes-sig-onprem-misc
 * kubernetes-sig-onprem-test-failures
 * kubernetes-sig-onprem-bugs
@@ -61,6 +62,8 @@ Name convention:
 * k8s-sig-foo-pr-reviews
 * k8s-sig-foo-api-reviews
 
+Note that there is no need for a k8s-sig-foo user.
+
 Example:
 
 * k8s-sig-onprem-misc
@@ -86,6 +89,8 @@ Name convention:
 * sig-foo-pr-reviews
 * sig-foo-api-reviews
 
+Note that there should not be a sig-foo team. We want to encourage contributors to select the most appropriate team to notify.
+
 Example:
 
 * sig-onprem-misc