diff options
| author | Aaron Crickenberger <spiffxp@google.com> | 2018-09-04 16:51:49 -0700 |
|---|---|---|
| committer | Aaron Crickenberger <spiffxp@google.com> | 2018-09-04 16:51:49 -0700 |
| commit | 50add93045328d0631a144dbdaa7546a2c2dc0e7 (patch) | |
| tree | 58193bda8250d4491af782977c7b63b85e35409d | |
| parent | eabdd5124f7857eceae2beaf22b906fdb9fa3c75 (diff) | |
Add sig retirement criteria
| -rw-r--r-- | committee-steering/governance/sig-governance.md | 18 |
1 files changed, 12 insertions, 6 deletions
diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 7ce7f76f..7edc2856 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -28,14 +28,12 @@ Subproject Owner Role. (this different from a SIG or Organization Member). through a [super-majority] vote between Chairs, Tech Leads and Subproject Owners. - Membership disagreements may be escalated to the SIG Chairs. SIG Chair membership disagreements may be escalated to the Steering Committee. - - Members *MAY* decide to step down at anytime and propose a replacement. Use lazy consensus amongst other members with fallback on majority vote to accept proposal. The candidate *SHOULD* be supported by a majority of SIG Members or Subproject Contributors (as applicable). - Members *MAY* select additional members through a [super-majority] vote amongst members. This *SHOULD* be supported by a majority of SIG Members or Subproject Contributors (as applicable). - ### Chair - Chair @@ -82,18 +80,19 @@ Subproject Owner Role. (this different from a SIG or Organization Member). - Defined in `SECURITY_CONTACTS` files, this is only relevant to the root file in the repository. Template [SECURITY_CONTACTS] -## Organizational management +## Organizational Management - SIG meets bi-weekly on zoom with agenda in meeting notes - *SHOULD* be facilitated by chairs unless delegated to specific Members - SIG overview and deep-dive sessions organized for Kubecon - *SHOULD* be organized by chairs unless delegated to specific Members - +- SIG updates to Kubernetes community meeting on a regular basis + - *SHOULD* be presented by chairs unless delegated to specific Members - Contributing instructions defined in the SIG CONTRIBUTING.md -### Project management +### Project Management -#### Subproject creation +#### Subproject Creation --- @@ -149,6 +148,13 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: - Option 1: SIG Technical Leads - Option 2: Federation of Subproject Owners +### SIG Retirement + +- In the event that the SIG is unable to regularly establish consistent quorum + or otherwise fulfill its Organizational Management responsibilities + - after 3 or more months it *SHOULD* be retired + - after 6 or more months it *MUST* be retired + [lazy-consensus]: http://communitymgt.wikia.com/wiki/Lazy_consensus [super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote [KEP]: https://github.com/kubernetes/community/blob/master/keps/0000-kep-template.md |