Commit 59ed303
doc: update CTC governance information
Update some outdated material. Provide some minor fixes. Wrap to 80
characters.
PR-URL: #7719
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Julien Gilli <jgilli@nodejs.org>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
Reviewed-By: Trevor Norris <trev.norris@gmail.com>1 parent 83cbf31 commit 59ed303
1 file changed
Lines changed: 19 additions & 26 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2,8 +2,8 @@ | |||
| 2 | 2 | ||
| 3 | 3 | ## Core Technical Committee | |
| 4 | 4 | ||
| 5 | - The Node.js project is jointly governed by a Core Technical Committee (CTC) | ||
| 6 | - which is responsible for high-level guidance of the project. | ||
| 5 | + The Node.js project is governed by a Core Technical Committee (CTC) which is | ||
| 6 | + responsible for high-level guidance of the project. | ||
| 7 | 7 | ||
| 8 | 8 | The CTC has final authority over this project including: | |
| 9 | 9 | ||
@@ -14,11 +14,6 @@ The CTC has final authority over this project including: | |||
| 14 | 14 | * Conduct guidelines | |
| 15 | 15 | * Maintaining the list of additional Collaborators | |
| 16 | 16 | ||
| 17 | - Initial membership invitations to the CTC were given to individuals who | ||
| 18 | - had been active contributors to Node.js, and who have significant | ||
| 19 | - experience with the management of the Node.js project. Membership is | ||
| 20 | - expected to evolve over time according to the needs of the project. | ||
| 21 | - | ||
| 22 | 17 | For the current list of CTC members, see the project | |
| 23 | 18 | [README.md](./README.md#current-project-team-members). | |
| 24 | 19 | ||
@@ -46,8 +41,8 @@ responsibility for the change. In the case of pull requests proposed | |||
| 46 | 41 | by an existing Collaborator, an additional Collaborator is required | |
| 47 | 42 | for sign-off. Consensus should be sought if additional Collaborators | |
| 48 | 43 | participate and there is disagreement around a particular | |
| 49 | - modification. See [Consensus Seeking Process](#consensus-seeking-process) below for further detail | ||
| 50 | - on the consensus model used for governance. | ||
| 44 | + modification. See [Consensus Seeking Process](#consensus-seeking-process) below | ||
| 45 | + for further detail on the consensus model used for governance. | ||
| 51 | 46 | ||
| 52 | 47 | Collaborators may opt to elevate significant or controversial | |
| 53 | 48 | modifications, or modifications that have not found consensus to the | |
@@ -87,9 +82,8 @@ members affiliated with the over-represented employer(s). | |||
| 87 | 82 | ||
| 88 | 83 | ## CTC Meetings | |
| 89 | 84 | ||
| 90 | - The CTC meets weekly on a Google Hangout On Air. The meeting is run by | ||
| 91 | - a designated moderator approved by the CTC. Each meeting should be | ||
| 92 | - published to YouTube. | ||
| 85 | + The CTC meets weekly in a voice conference call. The meeting is run by a | ||
| 86 | + designated moderator approved by the CTC. Each meeting is streamed on YouTube. | ||
| 93 | 87 | ||
| 94 | 88 | Items are added to the CTC agenda which are considered contentious or | |
| 95 | 89 | are modifications of governance, contribution policy, CTC membership, | |
@@ -100,32 +94,31 @@ That should happen continuously on GitHub and be handled by the larger | |||
| 100 | 94 | group of Collaborators. | |
| 101 | 95 | ||
| 102 | 96 | Any community member or contributor can ask that something be added to | |
| 103 | - the next meeting's agenda by logging a GitHub Issue. Any Collaborator, | ||
| 97 | + the next meeting's agenda by logging a GitHub issue. Any Collaborator, | ||
| 104 | 98 | CTC member or the moderator can add the item to the agenda by adding | |
| 105 | 99 | the ***ctc-agenda*** tag to the issue. | |
| 106 | 100 | ||
| 107 | - Prior to each CTC meeting, the moderator will share the Agenda with | ||
| 108 | - members of the CTC. CTC members can add any items they like to the | ||
| 109 | - agenda at the beginning of each meeting. The moderator and the CTC | ||
| 110 | - cannot veto or remove items. | ||
| 101 | + Prior to each CTC meeting, the moderator will share the agenda with | ||
| 102 | + members of the CTC. CTC members can also add items to the agenda at the | ||
| 103 | + beginning of each meeting. The moderator and the CTC cannot veto or remove | ||
| 104 | + items. | ||
| 111 | 105 | ||
| 112 | 106 | The CTC may invite persons or representatives from certain projects to | |
| 113 | 107 | participate in a non-voting capacity. | |
| 114 | 108 | ||
| 115 | - The moderator is responsible for summarizing the discussion of each | ||
| 116 | - agenda item and sending it as a pull request after the meeting. | ||
| 109 | + The moderator is responsible for summarizing the discussion of each agenda item | ||
| 110 | + and sending it as a pull request after the meeting. | ||
| 117 | 111 | ||
| 118 | 112 | ## Consensus Seeking Process | |
| 119 | 113 | ||
| 120 | 114 | The CTC follows a | |
| 121 | 115 | [Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) | |
| 122 | 116 | decision making model. | |
| 123 | 117 | ||
| 124 | - When an agenda item has appeared to reach a consensus, the moderator | ||
| 125 | - will ask "Does anyone object?" as a final call for dissent from the | ||
| 126 | - consensus. | ||
| 118 | + When an agenda item has appeared to reach a consensus, the moderator will ask | ||
| 119 | + "Does anyone object?" as a final call for dissent from the consensus. | ||
| 127 | 120 | ||
| 128 | - If an agenda item cannot reach a consensus, a CTC member can call for | ||
| 129 | - either a closing vote or a vote to table the issue to the next | ||
| 130 | - meeting. The call for a vote must be approved by a majority of the CTC | ||
| 131 | - or else the discussion will continue. Simple majority wins. | ||
| 121 | + If an agenda item cannot reach a consensus, a CTC member can call for either a | ||
| 122 | + closing vote or a vote to table the issue to the next meeting. The call for a | ||
| 123 | + vote must be approved by a simple majority of the CTC or else the discussion | ||
| 124 | + will continue. | ||
0 commit comments