Add new contact info for Paris and me

Add team calendar information
Add Zoom account specifics

sig-governance.md

@@ -18,17 +18,20 @@ In order to standardize Special Interest Group efforts, create maximum transpare
   variety of roles are represented
 - **SIG Lead**: SIG organizer
 
-## SIG creation procedure
+## SIG creation and maintenance procedure
 
 ### Prerequisites
 
 * 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 **@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 **@paris** or **@jorge**.  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 pyao@linuxfoundation.org cc'ing sarahnovotny@google.com.
- * Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com.
+ * Request a Zoom account from from **@paris** or **@jorge**. 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. 
+ * Calendars
+   - Add the meeting to the community meeting calendar by inviting cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com.
+   - If you want a team calendar ensure that it is managed with the SIG team lead list you will create (see below). Leads and jobs can change over time and it is important that no SIG resources are tied to a single user's account. 
 * 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.
@@ -52,6 +55,7 @@ Create Google Groups at [https://groups.google.com/forum/#!creategroup](https://
 Name convention:
 
 * kubernetes-sig-foo (the discussion group)
+* kubernetes-sig-foo-leads (list for the leads, to be used with Zoom and Calendars)
 * kubernetes-sig-foo-misc
 * kubernetes-sig-foo-test-failures
 * kubernetes-sig-foo-bugs