diff options
| author | Phillip Wittrock <pwittroc@google.com> | 2018-10-16 14:31:31 -0700 |
|---|---|---|
| committer | Phillip Wittrock <pwittroc@google.com> | 2018-10-16 14:33:14 -0700 |
| commit | cbcd362eeb60dd4cf1b3bc097ab0a62570cd6806 (patch) | |
| tree | 102c7e1962e4a124f51bab962957cee831aa3d0f /governance.md | |
| parent | 699174c491d9c8ba57addf62db776ae950c72b91 (diff) | |
Follow on working group gov
Diffstat (limited to 'governance.md')
| -rw-r--r-- | governance.md | 24 |
1 files changed, 3 insertions, 21 deletions
diff --git a/governance.md b/governance.md index 1c7d0807..ca4a6481 100644 --- a/governance.md +++ b/governance.md @@ -103,35 +103,17 @@ Subprojects for each SIG are documented in [sigs.yaml](sigs.yaml). We need community rallying points to facilitate discussions/work regarding topics that are short-lived or that span multiple SIGs. -This is the purpose of Working Groups (WG). The intent is to make -Working Groups relatively easy to create and to deprecate, once -inactive. - -Working groups do not own any code or subprojects. Instead, they are a place for -people to discuss topics that cross SIG boundaries. Working groups are primarily used to facilitate topics of discussion that are in scope for Kubernetes but that cross SIG lines. If a set of folks in the community want to get together and discuss a topic, they can do so without -forming a Working Group. As a community we will be looking for other ways to -highlight and encourage a larger ecosystem (with things like slack channels) -without offering any official endorsement. - -To propose a new working group, first find a SIG to sponsor the group. -Next, send a proposal to kubernetes-dev@googlegroups.com and also include -any potentially interested SIGs. Wait for public comment. If there's -enough interest, a new Working Group should be formed. +forming a Working Group. -Create a new mailing list in the from of kubernetes-wg-group-name. Working -groups typically have a Slack channel as well as regular meetings on zoom. -It's encouraged to keep a clear record of all accomplishments that's publicly -accessible. Like SIGs, working group communications and meetings should be -open and be recorded for later viewing. +See [working group governance] for more details about forming and disbanding +Working Groups. Working groups are documented in [sigs.yaml](sigs.yaml). -See [working group governance] for more details about forming and disbanding Working -Groups. ## Committees |