Commit a7ae887
governance: expand use of CTC issue tracker
As the CTC grows and has representation from more time zones, we need to
embrace asynchronous decision making and rely less on the actual
meeting. This change is a proposal for that which, ironically, probably
has to be approved at a meeting.
PR-URL: #8945
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Julien Gilli <jgilli@nodejs.org>
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Shigeki Ohtsu <ohtsu@ohtsu.org>1 parent f669a08 commit a7ae887
1 file changed
Lines changed: 21 additions & 12 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -23,14 +23,11 @@ The [nodejs/node](https://github.com/nodejs/node) GitHub repository is | |||
| 23 | 23 | maintained by the CTC and additional Collaborators who are added by the | |
| 24 | 24 | CTC on an ongoing basis. | |
| 25 | 25 | ||
| 26 | - Individuals making significant and valuable contributions are made | ||
| 27 | - Collaborators and given commit-access to the project. These | ||
| 28 | - individuals are identified by the CTC and their addition as | ||
| 29 | - Collaborators is discussed during the weekly CTC meeting. | ||
| 26 | + Individuals identified by the CTC as making significant and valuable | ||
| 27 | + contributions are made Collaborators and given commit access to the project. | ||
| 30 | 28 | ||
| 31 | 29 | _Note:_ If you make a significant contribution and are not considered | |
| 32 | - for commit-access, log an issue or contact a CTC member directly and it | ||
| 33 | - will be brought up in the next CTC meeting. | ||
| 30 | + for commit access, log an issue or contact a CTC member directly. | ||
| 34 | 31 | ||
| 35 | 32 | Modifications of the contents of the nodejs/node repository are made on | |
| 36 | 33 | a collaborative basis. Anybody with a GitHub account may propose a | |
@@ -44,11 +41,9 @@ participate and there is disagreement around a particular | |||
| 44 | 41 | modification. See [Consensus Seeking Process](#consensus-seeking-process) below | |
| 45 | 42 | for further detail on the consensus model used for governance. | |
| 46 | 43 | ||
| 47 | - Collaborators may opt to elevate significant or controversial | ||
| 48 | - modifications, or modifications that have not found consensus to the | ||
| 49 | - CTC for discussion by assigning the ***ctc-agenda*** tag to a pull | ||
| 50 | - request or issue. The CTC should serve as the final arbiter where | ||
| 51 | - required. | ||
| 44 | + Collaborators may opt to elevate significant or controversial modifications to | ||
| 45 | + the CTC by assigning the ***ctc-agenda*** tag to a pull request or issue. The | ||
| 46 | + CTC should serve as the final arbiter where required. | ||
| 52 | 47 | ||
| 53 | 48 | For the current list of Collaborators, see the project | |
| 54 | 49 | [README.md](./README.md#current-project-team-members). | |
@@ -127,7 +122,7 @@ group of Collaborators. | |||
| 127 | 122 | ||
| 128 | 123 | Any community member or contributor can ask that something be added to | |
| 129 | 124 | the next meeting's agenda by logging a GitHub issue. Any Collaborator, | |
| 130 | - CTC member or the moderator can add the item to the agenda by adding | ||
| 125 | + CTC member, or the moderator can add the item to the agenda by adding | ||
| 131 | 126 | the ***ctc-agenda*** tag to the issue. | |
| 132 | 127 | ||
| 133 | 128 | Prior to each CTC meeting, the moderator will share the agenda with | |
@@ -141,6 +136,20 @@ participate in a non-voting capacity. | |||
| 141 | 136 | The moderator is responsible for summarizing the discussion of each agenda item | |
| 142 | 137 | and sending it as a pull request after the meeting. | |
| 143 | 138 | ||
| 139 | + Due to the challenges of scheduling a global meeting with participants in | ||
| 140 | + several timezones, the CTC will seek to resolve as many agenda items as possible | ||
| 141 | + outside of meetings using | ||
| 142 | + [the CTC issue tracker](https://github.com/nodejs/CTC/issues). The process in | ||
| 143 | + the issue tracker is: | ||
| 144 | + | ||
| 145 | + * A CTC member opens an issue explaining the proposal/issue and @-mentions | ||
| 146 | + @nodejs/ctc. | ||
| 147 | + * After 72 hours, if there are two or more `LGTM`s from other CTC members and no | ||
| 148 | + explicit opposition from other CTC members, then the proposal is approved. | ||
| 149 | + * If there are any CTC members objecting, then a conversation ensues until | ||
| 150 | + either the proposal is dropped or the objecting members are persuaded. If | ||
| 151 | + there is an extended impasse, a motion for a vote may be made. | ||
| 152 | + | ||
| 144 | 153 | ## Consensus Seeking Process | |
| 145 | 154 | ||
| 146 | 155 | The CTC follows a | |
0 commit comments