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

Clarify the use of lazy consensus

This commit is contained in:
Carolyn Van Slyck 2018-07-13 12:54:47 -05:00
parent 287456a7d6
commit 22bd859023
No known key found for this signature in database
GPG Key ID: 1C91EA2338067CBF
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -132,7 +132,7 @@ The following, non-exhaustive, items are out of scope:
the `LGTM 1` and `LGTM 2` labels. the `LGTM 1` and `LGTM 2` labels.
- Pull requests that are labeled with `do-not-merge/hold` or have an on-going - Pull requests that are labeled with `do-not-merge/hold` or have an on-going
discussion must not be merged until all concerns are addressed. discussion must not be merged until all concerns are addressed.
- Disagreements are mainly resolved via consensus. In the event that a common - Disagreements are resolved via lazy consensus. In the event that a common
decision cannot be made, then a vote among the maintainers will be taken. decision cannot be made, then a vote among the maintainers will be taken.
Simple majority (>50%) wins. Simple majority (>50%) wins.