diff options
| author | Brandon Philips <brandon.philips@coreos.com> | 2018-07-02 16:32:49 -0700 |
|---|---|---|
| committer | Brandon Philips <brandon.philips@coreos.com> | 2018-07-02 16:32:49 -0700 |
| commit | 150be27d838831264ec564caf013e7124f931cd4 (patch) | |
| tree | 773f5639ff51f1f6c165a42e765f5126b373acee | |
| parent | 3cb6c7ab4bab939818a942c0c24893d8f521c7f9 (diff) | |
steering: governance: define chair removal process
As outlined by [Brian Grant](https://github.com/kubernetes/community/pull/2040#discussion_r189472207)
there isn't a process for a SIG Chair to be removed. I think the best
course is to suggest an unresponsive chair be encouraged to step down
and if that fails a consensus is reached amongst existing chairs and
subproject owners.
| -rw-r--r-- | committee-steering/governance/sig-governance-template-short.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/committee-steering/governance/sig-governance-template-short.md b/committee-steering/governance/sig-governance-template-short.md index 98aed04d..386e5291 100644 --- a/committee-steering/governance/sig-governance-template-short.md +++ b/committee-steering/governance/sig-governance-template-short.md @@ -10,11 +10,12 @@ Membership for roles tracked in: <link to OWNERS file> - Chairs *MAY* decide to step down at anytime and propose a replacement. Use lazy consensus amongst chairs with fallback on majority vote to accept proposal. This *SHOULD* be supported by a majority of SIG Members. - - Chairs *MAY* select additional chairs through a [super-majority] vote amongst chairs. This + - Chairs *MAY* select additional chairs through a [super-majority] vote amongst chairs. This *SHOULD* be supported by a majority of SIG Members. - Chairs *MUST* remain active in the role and are automatically removed from the position if they are unresponsive for > 3 months and *MAY* be removed if not proactively working with other chairs to fulfill - responsibilities. + responsibilities. Removal of a chair can be done either through a voluntary step down as outlined + above OR by a consensus of other chairs and SIG subproject owners. - Number: 2-3 - Defined in [sigs.yaml] |