kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Use lazy consensus with a 2/3 vote fallback for chair decisions

This commit is contained in:
Carolyn Van Slyck 2018-06-11 13:15:56 -05:00
parent eba966de67
commit 39b7c1d5ad
No known key found for this signature in database
GPG Key ID: 1C91EA2338067CBF
1 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
sig-service-catalog/charter.md
View File

@ -24,8 +24,10 @@ The following, non-exhaustive, items are out of scope:
- Maintainers - Maintainers
- Responsible for approving, and reviewing, pull requests. - Responsible for approving, and reviewing, pull requests.
- Responsible for technical planning and stewardship of the project. - Responsible for technical planning and stewardship of the project.
- New maintainers are nominated by a chair and require unanimous consent by all chairs. - New maintainers may be nominated by a chair, to accepted via lazy two-thirds
- Maintainers can be “retired” at the suggestion of a chair, and approved unanimously by the other chairs. resolution amongst the chairs.
- Maintainers may be nominated for removal from their position by a chair,
to accepted via lazy two-thirds resolution amongst the chairs.
- Chairs - Chairs
- All maintainer’s roles. - All maintainer’s roles.
@ -33,14 +35,16 @@ The following, non-exhaustive, items are out of scope:
in nature, such as organizing the weekly meetings. in nature, such as organizing the weekly meetings.
- A chair does not have more rights, or votes, than a maintainer. - A chair does not have more rights, or votes, than a maintainer.
- Responsible for reporting the SIG’s status to the appropriate Kubernetes leadership teams. - Responsible for reporting the SIG’s status to the appropriate Kubernetes leadership teams.
- Chairs MAY decide to step down at anytime and MAY propose a replacement, ideally from existing - All decisions amongst chairs are made using lazy consensus with a fallback to a 2/3 majority vote (lazy two-thirds resolution).
maintainers. Use lazy consensus amongst chairs with fallback on majority vote to accept proposal. This process is used for all decisions, such as changing chairs/maintainers or modifying this charter.
- Chairs MAY select additional chairs through a super-majority vote amongst chairs. - Chairs may nominate a new chair at any time, to be accepted via lazy two-thirds resolution amongst the chairs.
- Chairs MUST remain active in the role and MAY removed from the position - Chairs may decide to step down at any time. Before stepping down, the chair
if they are unresponsive for > 3 months or are not proactively working may propose and vote on their replacement via lazy two-thirds resolution amongst the chairs.
with other chairs to fulfill responsibilities. Use lazy consensus amongst chairs with - Chairs must remain active in the role and may be removed from the position
fallback on majority vote. via lazy two-thirds resolution amongst the chairs, if they are unresponsive
- Chairs may propose changes to this charter at any time. for > 3 months or are not proactively working with other chairs to fulfill responsibilities.
- Chairs may propose changes to this charter at any time, to be accepted via
lazy two-thirds resolution amongst the chairs.
- Emeritus Chairs ([Inspired by the Helm Project](http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html)) - Emeritus Chairs ([Inspired by the Helm Project](http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html))
- A chair who steps down may be given the title of Emeritus Chair. This title confers - A chair who steps down may be given the title of Emeritus Chair. This title confers