Remove creation of SIG service accounts
This commit is contained in:
Jorge O. Castro
parent
d1db844e6c
commit
62beba8bda
|
|
@ -46,98 +46,22 @@ Guidelines for drafting a SIG Charter can be found [here](/committee-steering/go
|
||||||
* Leads should [subscribe to the kubernetes-sig-leads mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-leads)
|
* 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.
|
* 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 service accounts for the SIG**
|
#### Creating a mailing list
|
||||||
|
|
||||||
With a purpose to distribute the channels of notification and discussion of the various topics, every SIG has to use multiple accounts to GitHub mentioning and notifications. Below the procedure is explained step-by-step.
|
Create a Google Group at [https://groups.google.com/forum/#!creategroup](https://groups.google.com/forum/#!creategroup), following the procedure:
|
||||||
|
|
||||||
NOTE: This procedure is managed and maintained by **[@idvoretskyi](https://github.com/idvoretskyi)**; please, reach him directly in case of any questions/suggestions.
|
Each SIG must have two discussion groups with the following settings.
|
||||||
|
|
||||||
#### **Google Groups creation**
|
- kubernetes-sig-foo (the discussion group):
|
||||||
|
- Anyone can view content.
|
||||||
Create Google Groups at [https://groups.google.com/forum/#!creategroup](https://groups.google.com/forum/#!creategroup), following the procedure:
|
- Anyone can join.
|
||||||
|
- Anyone can post.
|
||||||
* Each SIG should have one discussion groups, and a number of groups for mirroring relevant github notifications;
|
- Only members can view the list of members.
|
||||||
* Create groups using the name conventions below;
|
- kubernetes-sig-foo-leads (list for the leads, to be used with Zoom and Calendars)
|
||||||
* Groups should be created as e-mail lists with at least three owners (including sarahnovotny at google.com and ihor.dvoretskyi at gmail.com);
|
- Only members can view group content.
|
||||||
* 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";
|
- Anyone can apply to join.
|
||||||
* Set "View topics", "Post", "Join the Group" permissions to be "Public";
|
- Anyone can post.
|
||||||
|
- Only members can view the list of members.
|
||||||
Name convention:
|
- Groups should be created as e-mail lists with at least three owners (including parispittman 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 Paris and Ihor via email address (with a suitable welcome message); in Members/All Members select Ihor and Paris and assign to an "owner role"
|
||||||
* kubernetes-sig-foo (the discussion group)
|
- Set "View topics", "Post", "Join the Group" permissions to be "Public";
|
||||||
* 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
|
|
||||||
* kubernetes-sig-foo-feature-requests
|
|
||||||
* kubernetes-sig-foo-proposals
|
|
||||||
* kubernetes-sig-foo-pr-reviews
|
|
||||||
* kubernetes-sig-foo-api-reviews
|
|
||||||
|
|
||||||
Example:
|
|
||||||
|
|
||||||
* kubernetes-sig-onprem
|
|
||||||
* 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-mirror-foo-misc’ use ‘[kubernetes-sig-foo-misc@googlegroups.com](mailto:kubernetes-sig-foo-misc@googlegroups.com)’). After creating the GitHub users, please, add these users to the Kubernetes organization. If you don't have enough permissions to do that (by default, you don't), please request **@idvoretskyi** (backup person - **@sarahnovotny**) to help you with this. If GitHub contacts you about having too many robot accounts, please let us know.
|
|
||||||
|
|
||||||
|
|
||||||
Name convention:
|
|
||||||
|
|
||||||
* k8s-mirror-foo-misc
|
|
||||||
* k8s-mirror-foo-test-failures
|
|
||||||
* k8s-mirror-foo-bugs
|
|
||||||
* k8s-mirror-foo-feature-requests
|
|
||||||
* k8s-mirror-foo-proposals
|
|
||||||
* k8s-mirror-foo-pr-reviews
|
|
||||||
* k8s-mirror-foo-api-reviews
|
|
||||||
|
|
||||||
There is no need for a k8s-mirro-foo user.
|
|
||||||
|
|
||||||
Example:
|
|
||||||
|
|
||||||
* k8s-mirror-onprem-misc
|
|
||||||
* k8s-mirror-onprem-test-failures
|
|
||||||
* k8s-mirror-onprem-bugs
|
|
||||||
* k8s-mirror-onprem-feature-requests
|
|
||||||
* k8s-mirror-onprem-proposals
|
|
||||||
* k8s-mirror-onprem-pr-reviews
|
|
||||||
* k8s-mirror-onprem-api-reviews
|
|
||||||
|
|
||||||
NOTE: We have found that Github's notification autocompletion finds the users before the corresponding teams. This is the reason we recommend naming the users `k8s-mirror-foo-*` instead of `k8s-sig-foo-*`. If you previously created users named `k8s-sig-foo-*`, we recommend you rename them.
|
|
||||||
|
|
||||||
#### **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
|
|
||||||
|
|
||||||
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
|
|
||||||
* sig-onprem-test-failures
|
|
||||||
* sig-onprem-bugs
|
|
||||||
* sig-onprem-feature-requests
|
|
||||||
* sig-onprem-proposals
|
|
||||||
* sig-onprem-pr-reviews
|
|
||||||
* sig-onprem-api-reviews
|
|
||||||
Loading…
Reference in New Issue