From 32b54fb1b7d0dfd4eccd83dc9f7b2f2aecf9e20e Mon Sep 17 00:00:00 2001 From: parispittman Date: Wed, 20 Mar 2019 01:41:59 -0700 Subject: added calendar guidelines, rm from sig-wg-life, fixed related link --- sig-wg-lifecycle.md | 38 +++++++++++++++----------------------- 1 file changed, 15 insertions(+), 23 deletions(-) (limited to 'sig-wg-lifecycle.md') diff --git a/sig-wg-lifecycle.md b/sig-wg-lifecycle.md index 1c0d0102..0681fb56 100644 --- a/sig-wg-lifecycle.md +++ b/sig-wg-lifecycle.md @@ -3,18 +3,17 @@ This document covers everything you need to know about the creation and retirement (“lifecycle”) of a special interest or working group within the Kubernetes project. General project governance information can be found in the [steering committee repo]. Out of scope for this document: [subproject] creation. -[Creation] -[Retirement] -# [Creation] -## Prerequisites for a SIG +## [Creation] +### Prerequisites for a SIG - [ ] Read [sig-governance.md] -- [ ] Send an email to the Steering Committee to scope the SIG and get provisional approval. +- [ ] Send an email to the Steering Committee() to scope +the SIG and get provisional approval. - [ ] Look at the checklist below for processes and tips that you will need to do while this is going on. It's best to collect this information upfront so you have a smoother process to launch - [ ] Follow the [SIG charter process] to propose and obtain approval for a charter - [ ] Announce new SIG on kubernetes-dev@googlegroups.com -## Prerequisites for a WG +### Prerequisites for a WG - [ ] Read [wg-governance.md] - [ ] Send email to [kubernetes-dev@googlegroups.com] titled "WG-Creation-Request: WG Foo" with some of the questions answered from wg-goverance.md and wait for community discourse; ask for SIG sponsorship - [ ] Do the first checklist item in the #GitHub section below and add a row to the WG section: @@ -23,7 +22,7 @@ Out of scope for this document: [subproject] creation. - [ ] Place a `/hold` on it until the members that need to review have; a contributor experience member will do this for you if they don't see one already - [ ] Send an email to the stakeholder SIG mailing lists and steering committee with the sigs.yaml pull request -## GitHub: +### GitHub: - [ ] Submit a PR that will add rows to [sigs.yaml] using the [generator doc]; this will create README files and OWNERS_ALIASES files for your new directory in `kubernetes/community` - You’ll need: - SIG Name @@ -37,7 +36,7 @@ Out of scope for this document: [subproject] creation. - [ ] Add SIG-related docs like charter.md, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory once the above PR is merged. - [ ] File a [Kubernetes/Org] Issue for a label; read about our [GitHub management] services -## Communicate: +### Communicate: Each one of these has a linked canonical source guideline from set up to moderation and your role and responsibilities for each. We are all responsible for enforcing our [code of conduct]. - [ ] Read [moderation.md] and understand your role in keeping our community safe - [ ] Create your mailing lists - One for your members and another for your chairs/leads @@ -48,34 +47,26 @@ Each one of these has a linked canonical source guideline from set up to moderat - [ ] Request a YouTube playlist link [youtube-guidelines.md] - [ ] Request a zoom account [zoom-guidelines.md] -## Engage: +### Engage: ...as a chair/tech lead with other chairs/tech leads - [ ] Subscribe to the kubernetes-sig-leads@googlegroups.com group - [ ] Join the #chairs-and-techleads slack channel ...with the community as part of [sig-governance.md] - [ ] Get on the schedule for [Thursday community updates]; info at the top of the agenda -- [ ] Schedule your weekly/biweekly/at least every 3 weeks update meetings [TODO - THIS MAY CHANGE ONCE WE EXPLORE GSUITE] -- Use a poll service like doodle.com that will help you get a good pulse on your community and when they can meet -- This calendar creation process will allow all of your leads to edit SIG/WG Meetings. This is important as we all change jobs, email addresses, and take breaks from the project. Shared calendars will also provide consistenacy with contributors looking for your subproject meetings, office hours, and anything else that the SIG/WGs contributors should know about. -- Create a shared calendar on your own account. [example with google calendars: https://support.google.com/calendar/answer/37095?hl=en] Note: If you are creating from a corporate account like Google, it will not be public. Do a test first and ask a friend that doesn't work at your company. - - Name it “SIG/WG Foo [Time Cadence] Meetings” - - Sharing / access settings: Make it public - - Share it with full rights ("make changes and manage sharing”) with: cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com (Why this weird address? This is a public calendar that will be used to populate calendars on various sites) - - Your SIG/WG lead email distro (see second bullet in Communicate) - - Share it with lowest level of shown details (“see all event details”): - - SIG/WG membership distro (example: kubernetes-sig-foo@) +- [ ] Schedule your weekly/biweekly/triweekly [update meetings] and create your SIG/WG shared calendar. -# [Retirement] (merging or disbandment) +## [Retirement] +(merging or disbandment) Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may also merge with an existing SIG/WG if deemed appropriate, and would save project overhead in the long run. Working Groups in particular are more ephemeral than SIGs, so this process should be followed when the Working Group has accomplished it's mission. -## Prerequisites for SIG Retirement +### Prerequisites for SIG Retirement - [ ] SIG’s retirement decision follows the decision making and communication processes as outlined in their charter -## Prerequisites for WG Retirement +### Prerequisites for WG Retirement - [ ] Have completed the mission of the WG or have another reason as outlined in [wg-governance.md] -## Steps: +### Steps: - [ ] Send an email to kubernetes-dev@googlegroups.com and community@kubernetes.io alerting the community of your intentions to disband or merge. [example] - This kicks off the process for Contributor Experience’s community managers who will reach out and set an issue against `kubernetes/community` with exact next steps covered below. We can help walk through this when you get there. Most of this is covered in the same creation communication docs as above. - [ ] Archive the member and lead/chair mailing lists/[GoogleGroups] @@ -115,3 +106,4 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a [discuss-guidelines.md]: /communication/discuss-guidelines.md [Thursday community updates]: /events/community-meeting.md [example]: https://docs.google.com/document/d/1qZcAvuWBznR_oEaPWtwm7U4JNT91m8r9YOUvInU-src/edit#heading=h.jsw0l2t0ra8 +[update meetings]: /communication/calendar-guidelines.md -- cgit v1.2.3