Merge pull request #3 from spiffxp/sig-testing

sarahnovotny · sarahnovotny · commit ae6688a3d915 · 2016-05-12T16:08:37.000-07:00
Port over SIG table/docs from kubernetes.wiki
diff --git a/README.md b/README.md
@@ -14,77 +14,44 @@ Kubernetes uses [Slack](http://slack.com) for community discussions.
 
 To add new channels, contact one of the admins. Currently that includes briangrant, goltermann, jbeda, and thockin.
 
-## Special Interest Groups (SIG)
-
-Much of the community activity is organized into a community meeting and numerous SIGs. Each of those groups operates a little differently which is reflected in how they capture notes, examples, and other information. Each groups material is in its subdirectory in this project.
-
-The current SIGs are:
-
-### [Weekly Community Video Conference](community/README.md)
+## [Weekly Community Video Conference](community/README.md)
 
 The weekly community meeting provides an opportunity for the different SIGs and other parts of the community to come together.
 
-### SIG API Machinery
-
-The [Mission Doc](https://goo.gl/x5nWrF)
-
-### SIG Auth
-
-Kubernetes Special Interest Group for Authentication and Authorization.
-
-Goals for this SIG is to discuss improvements Kubernetes Authorization and Authentication, and cluster security policy. Not in scope for this SIG is to report specific vulnerabilities in Kubernetes, please report using these instructions: http://kubernetes.io/v1.1/docs/reporting-security-issues.html
-
-### SIG Autoscaling
-
-The scope of our SIG includes (but is not limited to):
-
-* autoscaling of clusters,
-* horizontal and vertical autoscaling of pods,
-* setting initial resources for pods,
-* topics related to monitoring pods and gathering their metrics (e.g.: Heapster)
-
-### SIG Cluster Ops
-
-SIG Cluster Ops Mission is to promote operability and interoperability of Kubernetes clusters.  We focus on shared operations practices for Kubernetes clusters with a goal to make kubernetes broadly accessible with a common baseline reference.  We also organize operators as a sounding board and advocacy group.
-
-### SIG Federation
-
-This is a SIG focused on Federation of Kubernetes Clusters ("Ubernetes") and related topics.  This includes:
-
-* Application resiliency against availability zone outages
-* Hybrid clouds
-* Spanning of multiple could providers
-* Application migration from private to public clouds (and vice versa)
-* ... and other similar subjects.
-
-### SIG Network
-
-This SIG is to promote and discuss network issues and operations.
-
-### SIG Node
-
-Mission Statement?
-
-### SIG OpenStack
-
-Mission Statement?
-
-### SIG Scalability
-
-Mission Statement?
-
-### SIG Scheduling
-
-Mission Statement?
-
-### SIG Storage
-
-The Kubernetes Storage Special-Interest-Group (SIG) is a working group within the Kubernetes contributor community interested in storage and volume plugins.
-
-### SIG Testing
-
-Mission Statement?
+## Special Interest Groups (SIG)
 
-### SIG UI
+Much of the community activity is organized into a community meeting and numerous SIGs. Each of those groups operates a little differently which is reflected in how they capture notes, examples, and other information. Each groups material is in its subdirectory in this project.
 
-Mission Statement?
+| Name | Leads | Group | Slack Channel | Meetings |
+|------|-------|-------|---------------|----------|
+| [API Machinery](sig-api-machinery/README.md) | [@lavalamp (Daniel Smith, Google)](https://github.com/lavalamp) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery) | [#sig-api-machinery](https://kubernetes.slack.com/messages/sig-api-machinery/) | Every other Wednesday at 11:00 AM PST |
+| [Auth](sig-auth/README.md) | [@ erictune (Eric Tune, Google)](https://github.com/erictune) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-auth) | [#sig-auth](https://kubernetes.slack.com/messages/sig-auth/) | Biweekly Wednesdays at 1100 to 1200 PT |
+| [Autoscaling](sig-autoscaling/README.md) | [@fgrzadkowski (Filip Grządkowski, Google)](https://github.com/jsz) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-autoscaling) | [#sig-autoscaling](https://kubernetes.slack.com/messages/sig-autoscaling/) | Biweekly (or triweekly) on Thurs at 0830 PT |
+| [AWS](sig-aws/README.md) | [@justinsb (Justin Santa Barbara)](https://github.com/justinsb)<br>[@mfburnett (Mackenzie Burnett)](https://github.com/mfburnett) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-aws) | [#sig-aws](https://kubernetes.slack.com/messages/sig-aws/) | TBD |
+| [Big Data](sig-big-data/README.md) | [@zmerlynn (Zach Loafman, Google)](https://github.com/zmerlynn)<br>[@timothysc (Timothy St. Clair, Red Hat)](https://github.com/timothysc)<br>[@wattsteve (Steve Watt, Red Hat)](https://github.com/wattsteve) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-big-data) | [#sig-big-data](https://kubernetes.slack.com/messages/sig-big-data/) | Bi-weekly on Mondays at 1300 PT |
+| [Cluster Ops] (sig-cluster-ops/README.md) | [@zehicle (Rob Hirschfeld, RackN)](https://github.com/zehicle) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-ops) | [#sig-cluster-ops](https://kubernetes.slack.com/messages/sig-cluster-ops) | Thursdays at 1:00 PM PST on [hangouts](https://plus.google.com/hangouts/_/google.com/sig-cluster-ops)|
+| [Configuration](sig-configuration/README.md) | [@jackgr (Jack Greenfield, Google)](https://github.com/jackgr)<br>[@bgrant0607 (Brian Grant, Google)](https://github.com/bgrant0607)<br>[@ghodss (Sam Ghods, Box)](https://github.com/ghodss) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-config) | [#sig-configuration](https://kubernetes.slack.com/messages/sig-configuration/) | Weekly on Wednesdays at 1300 PT |
+| [Federation](sig-federation/README.md) | [@quinton-hoole (Quinton Hoole, Google)](https://github.com/quinton-hoole) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-federation) | [#sig-federation](https://kubernetes.slack.com/messages/sig-federation/) | ??? |
+| [Network](sig-network/README.md) | [@thockin (Tim Hockin, Google)](https://github.com/thockin)<br> [@dcbw (Dan Williams, Red Hat)](https://github.com/dcbw) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-network) | [#sig-network](https://kubernetes.slack.com/messages/sig-network/) | (unknown frequency) 0700 Fridays |
+| [Node](sig-node/README.md) | [@dchen1107 (Dawn Chen, Google)](https://github.com/dchen1107)<br>[@jonboulle (Jonathan Boulle, CoreOS)](https://github.com/jonboulle)<br>[@derekwaynecarr (Derek Carr, Red Hat)](https://github.com/derekwaynecarr) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-node) | [#sig-node](https://kubernetes.slack.com/messages/sig-node/) | Weekly on Wednesdays at 11:00 PT |
+| [OpenStack](sig-openstack/README.md) | [@idvoretskyi (Ihor Dvoretskyi, Mirantis)] (https://github.com/idvoretskyi) <br> [@xsgordon (Steve Gordon, Redhat)] (https://github.com/xsgordon)| [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-openstack) | [#sig-openstack](https://kubernetes.slack.com/messages/sig-openstack/) | Biweekly on Tuesdays at 14:00 PT |
+| [Scalability](sig-scalability/README.md) | [@lavalamp (Daniel Smith, Google)](https://github.com/lavalamp)<br>[@countspongebob (Bob Wise, Samsung SDS)](https://github.com/countspongebob)<br>[@jbeda (Joe Beda)](https://github.com/jbeda) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-scale) | [#sig-scale](https://kubernetes.slack.com/messages/sig-scale/) | Weekly on Thursdays at 0900 PT |
+| [Scheduling](sig-scheduling/README.md) | [@davidopp (David Oppenheimer, Google)](https://github.com/davidopp)<br>[@timothysc (Timothy St. Clair, Red Hat)](https://github.com/timothysc) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling) | [#sig-scheduling](https://kubernetes.slack.com/messages/sig-scheduling/) | Alternate between Mondays at 1 PM PT and Wednesdays at 12:30 AM PT |
+| [Storage](sig-storage/README.md) | [@saad-ali (Saad Ali, Google)](https://github.com/saad-ali)<br>[@childsb (Brad Childs, Red Hat)](https://github.com/childsb) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-storage) | [#sig-storage](https://kubernetes.slack.com/messages/sig-storage/) | Bi-weekly Thursdays 9 AM PST (or more frequently) |
+| [Testing](sig-testing/README.md) | [@spiffxp (Aaron Crickenberger, Samsung)](https://github.com/spiffxp)<br>[@ixdy (Jeff Grafton, Google)](https://github.com/ixdy) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-testing) | [#sig-testing](https://kubernetes.slack.com/messages/sig-testing/) | [Tuesdays at 9:30 AM PT](https://zoom.us/j/553910341) |
+| [UI](sig-ui/README.md) | [@dodwyer (David O'Dwyer, Livewyer)](https://github.com/dodwyer)<br>[@preillyme (Patrick Reilly, Kismatic)](https://github.com/preillyme)<br> [@bryk (Piotr Bryk, Google)](https://github.com/bryk) | [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-ui) | [#sig-ui](https://kubernetes.slack.com/messages/sig-ui/) | Bi-weekly Wednesdays at 9 AM PT |
+| [Windows](sig-windows/README.md) | [@preillyme (Patrick Reilly, Kismatic)](https://github.com/preillyme)<br> [ @sschuller (Sinclair Schuller, Apprenda](https://github.com/sschuller)| [Group](https://groups.google.com/forum/#!forum/kubernetes-sig-windows) | [#sig-windows](https://kubernetes.slack.com/messages/sig-windows) | Bi-weekly Tuesdays at 10:00 AM PT |
+
+### How to start a SIG
+
+* Create a group with at least 2 owners: kubernetes-sig-foo@googlegroups.com
+  * Put a description of the topic in the welcome message
+* Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
+* If you wish, create a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo).  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. Can 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 add it to this wiki
+* Submit a PR to add any SIG-related docs, schedules, roadmaps, etc. to docs/devel/sigs/
+* 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`
diff --git a/sig-api-machinery/README.md b/sig-api-machinery/README.md
@@ -0,0 +1 @@
+[Mission Doc](https://goo.gl/x5nWrF)
diff --git a/sig-auth/README.md b/sig-auth/README.md
@@ -0,0 +1,23 @@
+Kubernetes SIG-Auth
+Kubernetes Special Interest Group for Authentication and Authorization
+
+
+Goals for this SIG:
+Discuss improvements Kubernetes Authorization and Authentication, and cluster security policy.
+Not in scope for this SIG:
+To report specific vulnerabilities in Kubernetes, please report using these instructions: http://kubernetes.io/v1.1/docs/reporting-security-issues.html
+
+General discussion of Linux security, or of containers is better directed to a non-Kubernetes mailing list.
+
+Proactive or general security discussion about Kubelet should go to kubernetes-sig-node@googlegroups.com.
+
+Proactive or general security discussion about the API server should go to kubernetes-sig-api-machinery@googlegroups.com.   
+
+
+
+Links/info:
+* Mailing list: https://groups.google.com/forum/#!pendingmember/kubernetes-sig-auth/apply
+* Github team: https://github.com/orgs/kubernetes/teams/sig-auth (Use ‘@kubernetes/sig-auth’ on github to notify team members.)
+* Slack channel: https://kubernetes.slack.com/messages/sig-auth/
+* Meeting frequency & time:  Biweekly on Wednesdays, 11am Pacific (see agenda for which Wednesdays)
+* Agenda & meeting notes: https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#
diff --git a/sig-autoscaling/README.md b/sig-autoscaling/README.md
@@ -0,0 +1,12 @@
+This is the wiki page of Kubernetes Autoscaling SIG: a special interest group for autoscaling related topics. The scope of our SIG includes (but is not limited to):
+
+* autoscaling of clusters,
+* horizontal and vertical autoscaling of pods,
+* setting initial resources for pods,
+* topics related to monitoring pods and gathering their metrics (e.g.: Heapster)
+
+[Meeting Notes](https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w/edit)
+
+[Hangout](https://plus.google.com/hangouts/_/google.com/k8s-autoscaling)
+
+Mailing list: kubernetes-sig-autoscaling@googlegroups.com
diff --git a/sig-aws/README.md b/sig-aws/README.md
@@ -0,0 +1 @@
+Mission Statement? Meeting Notes? Hangout Link?
diff --git a/sig-big-data/README.md b/sig-big-data/README.md
@@ -0,0 +1 @@
+[Meeting Notes](https://docs.google.com/document/d/1YhNLN39f5oZ4AHn_g7vBp0LQd7k37azL7FkWG8CEDrE/edit)
diff --git a/sig-cluster-ops/README.md b/sig-cluster-ops/README.md
@@ -0,0 +1,22 @@
+SIG Cluster Ops
+===============
+
+[Meeting Notes](https://docs.google.com/document/d/1IhN5v6MjcAUrvLd9dAWtKcGWBWSaRU8DNyPiof3gYMY/edit#)
+
+Meeting Time: Friday @ 1 PT (so we can end the week with Ops)
+
+[Google Group](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-ops)
+
+[Slack](https://kubernetes.slack.com/messages/sig-cluster-ops/)
+
+Co-leaders
+* Rob Hirschfeld (@zehicle, rob@rackn.com)
+* Mike Danese (@mikedanese)
+
+Mission
+-------
+
+SIG Cluster Ops Mission is to promote operability and interoperability of Kubernetes clusters.  We focus on shared operations practices for Kubernetes clusters with a goal to make kubernetes broadly accessible with a common baseline reference.  We also organize operators as a sounding board and advocacy group.
+
+
+[Hangouts](https://plus.google.com/hangouts/_/google.com/sig-cluster-ops), every Thursday at 1PM PST
diff --git a/sig-configuration/README.md b/sig-configuration/README.md
@@ -0,0 +1,11 @@
+This group is for discussion about application configuration and deployment in Kubernetes. We use the label `area/app-config-deployment` to tag related issues and pull requests on Github. 
+
+For Kubernetes cluster configuration and deployment, see [SIG-Cluster-Ops](SIG-Cluster-Ops).
+
+[Google group](https://groups.google.com/forum/#!forum/kubernetes-sig-config)
+
+[Slack](https://kubernetes.slack.com/messages/sig-configuration/)
+
+For access to the meeting agenda and notes, please join the Google group.
+* [Meeting Agenda and Notes](https://docs.google.com/document/d/1FZ_jiOdBZ_bfPD5Y3QMcfs2SCx956QLc9_E0QdR_l20/edit)
+
diff --git a/sig-federation/README.md b/sig-federation/README.md
@@ -0,0 +1,9 @@
+This is a SIG focused on Federation of Kubernetes Clusters ("Ubernetes") and related topics.  This includes:
+
+* Application resiliency against availability zone outages
+* Hybrid clouds
+* Spanning of multiple could providers
+* Application migration from private to public clouds (and vice versa)
+* ... and other similar subjects. 
+
+[Meeting Notes](https://docs.google.com/document/d/18mk62nOXE_MCSSnb4yJD_8UadtzJrYyJxFwbrgabHe8/edit#)
diff --git a/sig-network/README.md b/sig-network/README.md
@@ -0,0 +1 @@
+[This wiki has moved](https://github.com/kubernetes/community/wiki/SIG-Network)
diff --git a/sig-node/README.md b/sig-node/README.md
@@ -0,0 +1,3 @@
+[Meeting Notes](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit?usp=sharing)
+
+[Hangout](https://plus.google.com/hangouts/_/google.com/sig-node-meetup?authuser=0)
diff --git a/sig-openstack/README.md b/sig-openstack/README.md
@@ -0,0 +1,12 @@
+# OpenStack SIG
+
+**Leads:** Steve Gordon (@xsgordon) and Ihor Dvoretskyi (@idvoretskyi)
+
+**Slack Channel:** [#sig-openstack](https://kubernetes.slack.com/messages/sig-openstack/).  [Archive](http://kubernetes.slackarchive.io/sig-openstack/)
+
+**IRC:** #openstack-kubernetes on irc.freenode.net
+
+**Mailing List:** [kubernetes-sig-openstack](https://groups.google.com/forum/#!forum/kubernetes-sig-openstack)
+
+**Meetings:** Every second Tuesday at 2 PM PDT / 5 PM EDT. Video conference using Zoom, link is in the [notes](https://docs.google.com/document/d/1iAQ3LSF_Ky6uZdFtEZPD_8i6HXeFxIeW4XtGcUJtPyU/edit#
+)
diff --git a/sig-scalability/README.md b/sig-scalability/README.md
@@ -0,0 +1,28 @@
+# Scalability SIG
+
+**Leads:** Bob Wise (@countspongebob) and Joe Beda (@jbeda)
+
+**Slack Channel:** [#sig-scale](https://kubernetes.slack.com/messages/sig-scale/).  [Archive](http://kubernetes.slackarchive.io/sig-scale/)
+
+**Mailing List:** [kubernetes-sig-scale](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)
+
+**Meetings:** Thursdays at 9am pacific.  Contact Joe or Bob for invite. [Notes](https://docs.google.com/a/bobsplanet.com/document/d/1hEpf25qifVWztaeZPFmjNiJvPo-5JX1z0LSvvVY5G2g/edit?usp=drive_web
+)
+
+
+### Scalability SLAs
+
+We officially support two different SLAs:
+
+1. "API-responsiveness":
+   99% of all API calls return in less than 1s
+
+1. "Pod startup time:
+   99% of pods (with pre-pulled images) start within 5s
+
+This should be valid on appropriate hardware up to a 1000 node cluster with 30 pods/node.  We eventually want to expand that to 100 pods/node.
+
+For more details how do we measure those, you can look at: http://blog.kubernetes.io/2015_09_01_archive.html
+
+In the future we may want to add more SLAs (e.g. scheduler throughput), but we are not there yet.
+
diff --git a/sig-scheduling/README.md b/sig-scheduling/README.md
@@ -0,0 +1 @@
+Meeting notes? Hangout Link? Mission?
diff --git a/sig-storage/README.md b/sig-storage/README.md
@@ -0,0 +1,15 @@
+The Kubernetes Storage Special-Interest-Group (SIG) is a working group within the Kubernetes contributor community interested in storage and volume plugins.
+
+### Meeting
+We hold a public meeting every two weeks, on Thursdays at 9 AM (PST).
+* The meeting is held on Google Hangouts: https://plus.google.com/​hangouts/_/google.com/k8​s-sig-storage
+* Agenda and any notes from each meeting are captured in [this document](https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit?usp=sharing).
+
+### Links
+* Public Slack Channel: https://kubernetes.slack.com/messages/sig-storage/details/
+  * Get invite to join here: http://slack.k8s.io/
+* Google Group: https://groups.google.com/forum/#!forum/kubernetes-sig-storage
+* Github team: https://github.com/orgs/kubernetes/teams/sig-storage
+* Github issues: https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fstorage
+* Documentation for currently supported volume plugins: http://kubernetes.io/docs/user-guide/volumes/
+  * Volume plugin code can be found [here](https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fkubernetes%2Fkubernetes%2Ftree%2Fmaster%2Fpkg%2Fvolume&sa=D&sntz=1&usg=AFQjCNFKqi8vC-oTY46jEt8GBbwqm3619w).
diff --git a/sig-testing/README.md b/sig-testing/README.md
@@ -0,0 +1,34 @@
+# sig-testing
+
+The Kubernetes Testing SIG (sig-testing) is a working group within the Kubernetes contributor community interested in how we can most effectively test Kubernetes.  We’re interested specifically in making it easier for the community to run tests and contribute test results, to ensure Kubernetes is stable across a variety of cluster configurations and cloud providers.
+
+## video conference
+
+We meet weekly at 9:30am PDT (16:30pm UTC) at [this zoom room](https://zoom.us/j/553910341)
+
+## agenda
+
+We use [a public google doc](https://docs.google.com/document/d/1z8MQpr_jTwhmjLMUaqQyBk1EYG_Y_3D4y4YdMJ7V1Kk) to track proposed agenda items, as well as take notes during meetings.
+
+The agenda is open for comment.  Please contact the organizers listed below if you’d like to propose a topic.  Typically in the absence of anything formal we poll attendees for topics, and discuss tactical work.
+
+## slack
+
+[#sig-testing](https://kubernetes.slack.com/messages/sig-testing/) on kubernetes.slack.com
+Signup for access at http://slack.kubernetes.io/
+
+## github
+
+- [our github team: @kubernetes/sig-testing](https://github.com/orgs/kubernetes/teams/sig-testing)
+- [issues mentioning @kubernetes/sig-testing](https://github.com/issues?q=is%3Aopen+team%3Akubernetes%2Fsig-testing)
+
+We use the @kubernetes/sig-testing team to notify SIG members of particular issues or PR’s of interest.  If you would like to be added to this team, please contact the organizers listed below.
+
+## google group
+
+https://groups.google.com/forum/#!forum/kubernetes-sig-testing (FWIW this doesn't see a lot of traffic, come find us in slack!)
+
+## organizers
+
+- [Aaron Crickenberger, Samsung SDS](https://github.com/spiffxp), email: spiffxp@gmail.com
+- [Jeff Grafton, Google](https://github.com/ixdy), email: jgrafton@google.com
diff --git a/sig-ui/README.md b/sig-ui/README.md
@@ -0,0 +1 @@
+Mission Statement? Meeting Notes? Hangout Link?

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+Mission Statement? Meeting Notes? Hangout Link?`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+[Meeting Notes](https://docs.google.com/document/d/1YhNLN39f5oZ4AHn_g7vBp0LQd7k37azL7FkWG8CEDrE/edit)`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+[This wiki has moved](https://github.com/kubernetes/community/wiki/SIG-Network)`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+[Meeting Notes](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit?usp=sharing)`
	`2`	`+`
	`3`	`+[Hangout](https://plus.google.com/hangouts/_/google.com/sig-node-meetup?authuser=0)`