Skip to content

Commit

Permalink
Connect dots around SIG governance
Browse files Browse the repository at this point in the history
Signed-off-by: Joe Beda <joe.github@bedafamily.com>
  • Loading branch information
jbeda committed Apr 2, 2018
1 parent 3c91681 commit cbac840
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions sig-governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@

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
Expand All @@ -13,16 +14,14 @@ In order to standardize Special Interest Group efforts, create maximum transpare
* Use the above forums as the primary means of working, communicating, and collaborating, as opposed to private emails and meetings
* Represent the SIG for the PM group - see [PM SIG representatives](/sig-product-management/SIG%20PM%20representatives.md).

## SIG roles
- **SIG Participant**: active in one or more areas of the project; wide
variety of roles are represented
- **SIG Lead**: SIG organizer
[SIG charter process]: /committee-steering/governance/README.md

## SIG creation and maintenance procedure

### Prerequisites

* 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
* 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](http://kubernetes.slack.com) channel (#sig-foo) from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). New users can join at [slack.kubernetes.io](http://slack.kubernetes.io).
* 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`
Expand Down

0 comments on commit cbac840

Please sign in to comment.