Commit 3ee94f2
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 <myles.borins@gmail.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent cfcf948 commit 3ee94f2
1 file changed
Lines changed: 11 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -36,10 +36,17 @@ Collaborators. All pull requests must be reviewed and accepted by a | |||
| 36 | 36 | Collaborator with sufficient expertise who is able to take full | |
| 37 | 37 | responsibility for the change. In the case of pull requests proposed | |
| 38 | 38 | 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. | ||
| 43 | 50 | ||
| 44 | 51 | Collaborators may opt to elevate significant or controversial modifications to | |
| 45 | 52 | the CTC by assigning the `ctc-review` label to a pull request or issue. The | |
0 commit comments