Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how the TOC will make decisions #15

Closed
chipchilders opened this issue Sep 25, 2020 · 3 comments · Fixed by #49
Closed

Document how the TOC will make decisions #15

chipchilders opened this issue Sep 25, 2020 · 3 comments · Fixed by #49
Assignees
Labels

Comments

@chipchilders
Copy link
Contributor

Perhaps:

Aim for consensus first, vote if no consensus possible in a reasonable timeframe.

How many votes are needed to make a decision in the affirmative?

@chipchilders
Copy link
Contributor Author

@troytop says he has a good description of "consensus" somewhere

@bkrannich
Copy link
Contributor

@chipchilders: Plus, there's the one one of my colleagues suggested for the bylaws: "Consensus is defined as the lack of sustained objection."

@troytop
Copy link

troytop commented Jan 8, 2021

Turns out the document I was thinking of was not a description of consensus decision making, but a table of agreed terminology to use for group decisions. I can't attribute this properly because I don't remember where it comes from originally.

Description Term
Best choice, cannot be improved upon PERFECT
We all agree and support without reservation CONSENSUS
The details may not be perfect, but it is close enough for me to support it here at the table and outside this meeting as well. INFORMED CONSENT
I have reservations, I would like more discussion. I may then move up to consensus or informed consent; move down to concern; or agree that you can decide. I will not second-guess your decision outside this meeting. RESERVATION
I have fundamental concerns; I am not able to support this choice at this time. CONCERN
I do not agree, this is in conflict with my values and beliefs. DISAGREEMENT

emalm added a commit to emalm/community that referenced this issue Jan 15, 2021
Initial draft of a proposal to resolve cloudfoundry#15, as a simplification of the draft at cloudfoundry#25.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants