Connect dots around SIG governance

Signed-off-by: Joe Beda <joe.github@bedafamily.com>

1 files changed, 11 insertions, 8 deletions

diff --git a/sig-governance.md b/sig-governance.md
index 1613607b..4f6e857c 100644
--- a/sig-governance.md
+++ b/sig-governance.md
@@ -2,6 +2,7 @@
 
 In order to standardize Special Interest Group efforts, create maximum transparency, and route contributors to the appropriate SIG, SIGs should follow the guidelines stated below:
 
+* Create a charter and have it approved according to the [SIG charter process]
 * Meet regularly, at least for 30 minutes every 3 weeks, except November and December
 * Keep up-to-date meeting notes, linked from the SIG's page in the community repo
 * Announce meeting agenda and minutes after each meeting, on their SIG mailing list
@@ -9,7 +10,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare
 * Ensure the SIG's mailing list and slack channel are archived
 * Report activity in the weekly community meeting at least once every 6 weeks
 * Participate in release planning meetings and retrospectives, and burndown meetings, as needed
-* Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc. 
+* Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc.
 * Use the above forums as the primary means of working, communicating, and collaborating, as opposed to private emails and meetings
 
 In addition, SIGs have the following responsibilities to SIG PM:
@@ -18,19 +19,21 @@ In addition, SIGs have the following responsibilities to SIG PM:
 * actively track / maintain SIG features within [k/features](https://github.com/kubernetes/features)
 * attend [SIG PM](/sig-pm/README.md) meetings, as needed / requested
 
+[SIG charter process]: /committee-steering/governance/README.md
+
 ## SIG Roles
 
-Defining SIG Roles is a function of the SIG Charter.  
+Defining SIG Roles is a function of the SIG Charter.
 Guidelines for drafting a SIG Charter can be found [here](/committee-steering/governance/README.md).
 
-
 ## SIG creation and maintenance procedure
 
 ### Prerequisites
 
-* Propose the new SIG publicly, including a brief mission statement, by emailing kubernetes-dev@googlegroups.com and posting to discuss.kubernetes.io, 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 the #slack-admins channel.  New users can join at [slack.kubernetes.io](http://slack.kubernetes.io).
+* Work with the Steering Committee to scope the SIG and get provisional approval.
+  Follow the [SIG charter process] to propose and obtain approval for a charter.
+* 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).
 * 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.
  * Read [how to use YouTube](/communication/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel.
@@ -41,13 +44,13 @@ Guidelines for drafting a SIG Charter can be found [here](/committee-steering/go
    4. Share it with the SIG mailing list, lowest privileges.
    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 
+* Announce new SIG on kubernetes-dev@googlegroups.com
 * Leads should [subscribe 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 a mailing list
 
-Create a Google Group at [https://groups.google.com/forum/#!creategroup](https://groups.google.com/forum/#!creategroup), following the procedure: 
+Create a Google Group at [https://groups.google.com/forum/#!creategroup](https://groups.google.com/forum/#!creategroup), following the procedure:
 
 Each SIG must have two discussion groups with the following settings.