From fdb3d8c76ebf01d3ecf9c7a24720297e554ca55f Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Wed, 21 Dec 2016 14:10:04 +0200 Subject: [PATCH 1/5] Create sig-creation-procedure.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Following up the discussion, initiated at https://groups.google.com/forum/#!topic/kubernetes-dev/LEtIxeG0i84 and https://github.com/kubernetes/community/pull/90, this procedure describes the process of creating the new SIG (as well as optimizing the existing ones) within the Kubernetes community. These steps were performed and reproduced for the newly created SIG-OnPrem, existing SIG’s should be updated via this procedure as well. --- sig-creation-procedure.md | 83 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 sig-creation-procedure.md diff --git a/sig-creation-procedure.md b/sig-creation-procedure.md new file mode 100644 index 00000000000..d2c53e23fdf --- /dev/null +++ b/sig-creation-procedure.md @@ -0,0 +1,83 @@ +### SIG creation procedure + +#### +**Create the GitHub teams** + +Create the GitHub teams at [https://github.com/orgs/kubernetes/new-team](https://github.com/orgs/kubernetes/new-team), using the following name convention: + +* sig-foo-misc +* sig-foo-test-failures +* sig-foo-bugs +* sig-foo-feature-requests +* sig-foo-proposals +* sig-foo-pr-reviews +* sig-foo-api-reviews + +I.e: + +* sig-onprem-misc +* sig-onprem-test-failures +* sig-onprem-bugs +* sig-onprem-feature-requests +* sig-onprem-proposals +* sig-onprem-pr-reviews +* sig-onprem-api-reviews + +#### +**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); +* 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-misc +* kubernetes-sig-foo-test-failures +* kubernetes-sig-foo-bugs +* kubernetes-sig-foo-feature-requests +* kubernetes-sig-foo-proposals +* kubernetes-sig-foo-pr-reviews +* kubernetes-sig-foo-api-reviews + +I.e: + +* kubernetes-sig-onprem-misc +* kubernetes-sig-onprem-test-failures +* kubernetes-sig-onprem-bugs +* kubernetes-sig-onprem-feature-requests +* kubernetes-sig-onprem-proposals +* kubernetes-sig-onprem-pr-reviews +* kubernetes-sig-onprem-api-reviews + +#### +**GitHub users creation** + +Create the GitHub users at [https://github.com/join](https://github.com/join), using the name convention below. + +As an e-mail address, please, use the Google Group e-mail address of the respective Google Group, created before (i.e. - for user ‘k8s-sig-foo-misc’ use ‘[kubernetes-sig-foo-misc@googlegroups.com](mailto:kubernetes-sig-foo-misc@googlegroups.com)’). After creating the GitHub users, please, request @idvoretskyi (backup person - @sarahnovotny) to add these users to the Kubernetes organization. + + +Name convention: + +* k8s-sig-foo-misc +* k8s-sig-foo-test-failures +* k8s-sig-foo-bugs +* k8s-sig-foo-feature-requests +* k8s-sig-foo-proposals +* k8s-sig-foo-pr-reviews +* k8s-sig-foo-api-reviews + +I.e: + +* k8s-sig-onprem-misc +* k8s-sig-onprem-test-failures +* k8s-sig-onprem-bugs +* k8s-sig-onprem-feature-requests +* k8s-sig-onprem-proposals +* k8s-sig-onprem-pr-reviews +* k8s-sig-onprem-api-reviews From d3947bb46b87fb9cc0d315d4dfe87cc3d9c1176e Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Thu, 22 Dec 2016 17:57:21 +0200 Subject: [PATCH 2/5] "Example" instead of "i.e" fix --- sig-creation-procedure.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sig-creation-procedure.md b/sig-creation-procedure.md index d2c53e23fdf..8b873c099c9 100644 --- a/sig-creation-procedure.md +++ b/sig-creation-procedure.md @@ -13,7 +13,7 @@ Create the GitHub teams at [https://github.com/orgs/kubernetes/new-team](https:/ * sig-foo-pr-reviews * sig-foo-api-reviews -I.e: +Example: * sig-onprem-misc * sig-onprem-test-failures @@ -44,7 +44,7 @@ Name convention: * kubernetes-sig-foo-pr-reviews * kubernetes-sig-foo-api-reviews -I.e: +Example: * kubernetes-sig-onprem-misc * kubernetes-sig-onprem-test-failures @@ -72,7 +72,7 @@ Name convention: * k8s-sig-foo-pr-reviews * k8s-sig-foo-api-reviews -I.e: +Example: * k8s-sig-onprem-misc * k8s-sig-onprem-test-failures From d7bdd275cec514fbe54ad08616416d6899d68acf Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Thu, 22 Dec 2016 18:04:59 +0200 Subject: [PATCH 3/5] GitHub teams update (and moved to the bottom) --- sig-creation-procedure.md | 48 ++++++++++++++++++++------------------- 1 file changed, 25 insertions(+), 23 deletions(-) diff --git a/sig-creation-procedure.md b/sig-creation-procedure.md index 8b873c099c9..37519e6d098 100644 --- a/sig-creation-procedure.md +++ b/sig-creation-procedure.md @@ -1,28 +1,5 @@ ### SIG creation procedure -#### -**Create the GitHub teams** - -Create the GitHub teams at [https://github.com/orgs/kubernetes/new-team](https://github.com/orgs/kubernetes/new-team), using the following name convention: - -* sig-foo-misc -* sig-foo-test-failures -* sig-foo-bugs -* sig-foo-feature-requests -* sig-foo-proposals -* sig-foo-pr-reviews -* sig-foo-api-reviews - -Example: - -* sig-onprem-misc -* sig-onprem-test-failures -* sig-onprem-bugs -* sig-onprem-feature-requests -* sig-onprem-proposals -* sig-onprem-pr-reviews -* sig-onprem-api-reviews - #### **Google Groups creation** @@ -81,3 +58,28 @@ Example: * k8s-sig-onprem-proposals * k8s-sig-onprem-pr-reviews * k8s-sig-onprem-api-reviews + +#### +**Create the GitHub teams** + +Create the GitHub teams at [https://github.com/orgs/kubernetes/new-team](https://github.com/orgs/kubernetes/new-team), using the name convention below. Please, add the GitHub users (created before) to the GitHub teams respectively. + +Name convention: + +* sig-foo-misc +* sig-foo-test-failures +* sig-foo-bugs +* sig-foo-feature-requests +* sig-foo-proposals +* sig-foo-pr-reviews +* sig-foo-api-reviews + +Example: + +* sig-onprem-misc +* sig-onprem-test-failures +* sig-onprem-bugs +* sig-onprem-feature-requests +* sig-onprem-proposals +* sig-onprem-pr-reviews +* sig-onprem-api-reviews From d6c9247d5b9eeaadaafe81277170fc26f711b3d0 Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Mon, 9 Jan 2017 19:49:44 +0200 Subject: [PATCH 4/5] full procedure in one file --- sig-creation-procedure.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/sig-creation-procedure.md b/sig-creation-procedure.md index 37519e6d098..cb59728588c 100644 --- a/sig-creation-procedure.md +++ b/sig-creation-procedure.md @@ -1,5 +1,17 @@ ### 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). +* 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` + #### **Google Groups creation** From 0eb833563b918bf9cadb404f1b7b6aea6ab7cde6 Mon Sep 17 00:00:00 2001 From: Ihor Dvoretskyi Date: Mon, 9 Jan 2017 19:54:28 +0200 Subject: [PATCH 5/5] "How to start a SIG" linked to the new instruction --- README.md | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/README.md b/README.md index 72e00942258..cfc67810d18 100644 --- a/README.md +++ b/README.md @@ -68,18 +68,4 @@ The community meeting calendar is available as an [iCal to subscribe to] (https: | [UI](sig-ui/README.md) | [@romlein (Dan Romlein, Apprenda)](https://github.com/romlein)
[@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/) | Wednesdays at 4:00 PM CEST | | [Windows](sig-windows/README.md) | [@michmike77 (Michael Michael, Apprenda)](https://github.com/michmike)| [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 - -* 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 with at least 2 owners (and one of which should be sarahnovotny at google.com): kubernetes-sig-foo@googlegroups.com - * Put a description of the topic in the welcome message - * Set "Join the group" and "Post" to "Public" -* 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). -* 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` +### [How to start a SIG](sig-creation-procedure.md)