diff options
| author | Rich Trott <rtrott@gmail.com> | 2016-10-12 21:34:44 -0700 |
|---|---|---|
| committer | James M Snell <jasnell@gmail.com> | 2016-10-19 08:35:15 -0700 |
| commit | add885416f38020f84b544b3cc0be28d6cf59bdc (patch) | |
| tree | eddd50f77076eabe301b20339a07684d66b11b81 /GOVERNANCE.md | |
| parent | 92ece8671a3da8910bc8755b16ac121ba300a122 (diff) | |
| download | android-node-v8-add885416f38020f84b544b3cc0be28d6cf59bdc.tar.gz android-node-v8-add885416f38020f84b544b3cc0be28d6cf59bdc.tar.bz2 android-node-v8-add885416f38020f84b544b3cc0be28d6cf59bdc.zip | |
doc: add ctc-review label information
PR-URL: https://github.com/nodejs/node/pull/9072
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Diffstat (limited to 'GOVERNANCE.md')
| -rw-r--r-- | GOVERNANCE.md | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/GOVERNANCE.md b/GOVERNANCE.md index a61d9848b1..86796ef03d 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -42,7 +42,7 @@ modification. See [Consensus Seeking Process](#consensus-seeking-process) below for further detail on the consensus model used for governance. Collaborators may opt to elevate significant or controversial modifications to -the CTC by assigning the ***ctc-agenda*** tag to a pull request or issue. The +the CTC by assigning the `ctc-review` label to a pull request or issue. The CTC should serve as the final arbiter where required. For the current list of Collaborators, see the project @@ -98,7 +98,7 @@ members affiliated with the over-represented employer(s). Typical activities of a CTC member include: * attending the weekly meeting -* commenting on the weekly CTC meeting issue and issues labeled `ctc-agenda` +* commenting on the weekly CTC meeting issue and issues labeled `ctc-review` * participating in CTC email threads * volunteering for tasks that arise from CTC meetings and related discussions * other activities (beyond those typical of Collaborators) that facilitate the @@ -120,10 +120,12 @@ The intention of the agenda is not to approve or review all patches. That should happen continuously on GitHub and be handled by the larger group of Collaborators. -Any community member or contributor can ask that something be added to -the next meeting's agenda by logging a GitHub issue. Any Collaborator, -CTC member, or the moderator can add the item to the agenda by adding -the ***ctc-agenda*** tag to the issue. +Any community member or contributor can ask that something be reviewed +by the CTC by logging a GitHub issue. Any Collaborator, CTC member, or the +moderator can bring the issue to the CTC's attention by applying the +`ctc-review` label. If consensus-seeking among CTC members fails for a +particular issue, it may be added to the CTC meeting agenda by adding the +`ctc-agenda` label. Prior to each CTC meeting, the moderator will share the agenda with members of the CTC. CTC members can also add items to the agenda at the |