community/sig-governance.md

SIG Governance

In order to standardize Special Interest Group efforts, create maximum transparency, and route contributors to the appropriate SIG, SIGs should follow the guidelines stated below:

• Create a charter and have it approved according to the SIG charter process
• Meet regularly, at least for 30 minutes every 3 weeks, except November and December
• Keep up-to-date meeting notes, linked from the SIG's page in the community repo
• Announce meeting agenda and minutes after each meeting, on their SIG mailing list
• Record SIG meeting and make it publicly available
• Ensure the SIG's mailing list and slack channel are archived
• Report activity in the weekly community meeting at least once every 6 weeks
• Participate in release planning meetings and retrospectives, and burndown meetings, as needed
• Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc.
• Use the above forums as the primary means of working, communicating, and collaborating, as opposed to private emails and meetings

In addition, SIGs have the following responsibilities to SIG PM:

• identify SIG annual roadmap
• identify all SIG features in the current release
• actively track / maintain SIG features within k/features
• attend SIG PM meetings, as needed / requested

SIG Roles

Defining SIG Roles is a function of the SIG Charter. Guidelines for drafting a SIG Charter can be found here.

SIG creation and maintenance procedure

Prerequisites

• Work with the Steering Committee to scope the SIG and get provisional approval. Follow the SIG charter process to propose and obtain approval for a charter.
• Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo
• Request a new kubernetes.slack.com channel (#sig-foo) from @parispittman or @castrojo. New users can join at slack.kubernetes.io.
• Organize video meetings as needed. No need to wait for the Weekly Community Video Conference to discuss. Please report summary of SIG activities there.
• Request a Zoom account by emailing Paris Pittman(parispittman@google.com) and Jorge Castro(jorge@heptio.com). 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 for publishing your videos to the Kubernetes channel.
• Calendars
  1. Create a calendar on your own account. Make it public.
  2. Share it with all SIG leads with full ownership of the calendar - they can edit, rename, or even delete it.
  3. Share it with sc1@kubernetes.io, sc2@kubernetes.io, sc3@kubernetes.io, with full ownership. This is just in case SIG leads ever disappear.
  4. Share it with the SIG mailing list, lowest privileges.
  5. Share individual events with cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com to publish on the universal calendar.
• Use existing proposal and PR process (to be documented)
• Announce new SIG on kubernetes-dev@googlegroups.com
• Leads should subscribe to the kubernetes-sig-leads mailing list
• 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 a mailing list

Create a Google Group at https://groups.google.com/forum/#!creategroup, following the procedure:

Each SIG must have two discussion groups with the following settings.

• kubernetes-sig-foo (the discussion group):
  • Anyone can view content.
  • Anyone can join.
  • Anyone can post.
  • Only members can view the list of members.
• kubernetes-sig-foo-leads (list for the leads, to be used with Zoom and Calendars)
  • Only members can view group content.
  • Anyone can apply to join.
  • Anyone can post.
  • Only members can view the list of members.
• 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"
• Set "View topics", "Post", "Join the Group" permissions to be "Public";