Skip to content

Commit 3b839d1

Browse files
TrottMyles Borins
authored and
Myles Borins
committed
doc: remove confusing reference in governance doc
At the CTC meeting today, Sakthipriyan noted that there was a link to the CTC consensus material from the pull request consensus material. The link was confusing because the CTC consensus material is meeting-specific, which does not apply to pull requests. I have removed that link and replaced it with a text explanation. PR-URL: #9073 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent e564cb6 commit 3b839d1

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

GOVERNANCE.md

+11-4
Original file line numberDiff line numberDiff line change
@@ -36,10 +36,17 @@ Collaborators. All pull requests must be reviewed and accepted by a
3636
Collaborator with sufficient expertise who is able to take full
3737
responsibility for the change. In the case of pull requests proposed
3838
by an existing Collaborator, an additional Collaborator is required
39-
for sign-off. Consensus should be sought if additional Collaborators
40-
participate and there is disagreement around a particular
41-
modification. See [Consensus Seeking Process](#consensus-seeking-process) below
42-
for further detail on the consensus model used for governance.
39+
for sign-off.
40+
41+
If one or more Collaborators oppose a proposed change, then the change can not
42+
be accepted unless:
43+
44+
* Discussions and/or additional changes result in no Collaborators objecting to
45+
the change. Previously-objecting Collaborators do not necessarily have to
46+
sign-off on the change, but they should not be opposed to it.
47+
* The change is escalated to the CTC and the CTC votes to approve the change.
48+
This should be used only after other options (especially discussion among
49+
the disagreeing Collaborators) have been exhausted.
4350

4451
Collaborators may opt to elevate significant or controversial modifications to
4552
the CTC by assigning the `ctc-review` label to a pull request or issue. The

0 commit comments

Comments
 (0)