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 /committee-steering/governance | |
| parent | 699174c491d9c8ba57addf62db776ae950c72b91 (diff) | |
Follow on working group gov
Diffstat (limited to 'committee-steering/governance')
| -rw-r--r-- | committee-steering/governance/wg-governance.md | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/committee-steering/governance/wg-governance.md b/committee-steering/governance/wg-governance.md index 63c450b1..3c478b3d 100644 --- a/committee-steering/governance/wg-governance.md +++ b/committee-steering/governance/wg-governance.md @@ -1,7 +1,5 @@ # Kubernetes Working Group Formation and Disbandment -Draft 1.0 // Jaice Singer DuMars // June, 2018 - ## Process Overview and Motivations Working Groups provide a formal avenue for disparate groups to collaborate around a common problem, craft a balanced position, and disband. Because they represent the interests of multiple groups, they are a vehicle for consensus @@ -62,8 +60,7 @@ requirements for that are: - chair information - meeting information - contact methods -- any sig stakeholders -- any subproject stakeholders +- any [sig or subproject](sig-governance.md#project-management) stakeholders The pull request should be labeled with any SIG stakeholders and committee/steering. And since GitHub notifications are not a reliable means to contact people, an email should be sent to the mailing lists for the stakeholder SIGs, @@ -92,7 +89,7 @@ Working Groups will be disbanded if either of the following is true: - Zoom The current Chair may step down at any time. When they do so, a new Chair may be selected through lazy consensus -within the Working Group. +within the Working Group, and [sigs.yaml](../../sigs.yaml) should be updated. References |
