...
| Info | ||
|---|---|---|
| ||
This consultation is now closed. It was open from June 13, 2018 to July 17, 2018. The final document is here. |
Background
InCommon's Community Trust and Assurance Board (CTAB) is seeking feedback on the proposed Community Consensus Process. The document outlines repeatable steps the CTAB will use to facilitate community discussion and consensus in support of Baseline Expectations for Trust in Federation. This process is iterative and will change over time as the community gains experience at answering questions of consensus.
...
| Number | Current Text | Proposed Text / Query / Suggestion | Proposer | +1 (add your name here if you agree with the proposal) | Action (please leave this column blank) |
|---|---|---|---|---|---|
| 1 | e. Communication continues until rough consensus is achieved. | Rough consensus seems to be a bit ambiguous compared to the concreteness of the rest of this process. What does it mean? That most participants in the discussion agree? That everyone at least sort of agrees? Also, the process doesn’t say who will arbitrate or make the final call should rough consensus not occur. | Keith Wessel | Added a footnote which describes rough consensus: We do not require complete unanimity, but strive to achieve a point where all issues brought forward have been considered and we can continue moving. See RFC7282, "On Consensus and Humming in the IETF." | |
See Also