diff options
| author | Rich Trott <rtrott@gmail.com> | 2019-03-07 19:49:22 -0800 |
|---|---|---|
| committer | Rich Trott <rtrott@gmail.com> | 2019-03-09 22:25:19 -0800 |
| commit | b4e24e3c96ef404815cb232f4e3e7b87629477a1 (patch) | |
| tree | a26b769282f85d4b7f90990e7b67c9791d2c938d /GOVERNANCE.md | |
| parent | 6e81a959d0b1d23ecc0ae96ce969da8192ad60f9 (diff) | |
| download | android-node-v8-b4e24e3c96ef404815cb232f4e3e7b87629477a1.tar.gz android-node-v8-b4e24e3c96ef404815cb232f4e3e7b87629477a1.tar.bz2 android-node-v8-b4e24e3c96ef404815cb232f4e3e7b87629477a1.zip | |
doc: remove tsc-review
The tsc-review label is ineffective. It almost always gets ignored.
Remove it. When requiring TSC attention, people should @-mention the
TSC GitHub team.
PR-URL: https://github.com/nodejs/node/pull/26506
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Diffstat (limited to 'GOVERNANCE.md')
| -rw-r--r-- | GOVERNANCE.md | 12 |
1 files changed, 3 insertions, 9 deletions
diff --git a/GOVERNANCE.md b/GOVERNANCE.md index d92d3c821e..11499b4c78 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -50,10 +50,6 @@ be accepted unless: This should only happen if disagreements between Collaborators cannot be resolved through discussion. -Collaborators may opt to elevate significant or controversial modifications to -the TSC by assigning the `tsc-review` label to a pull request or issue. The -TSC should serve as the final arbiter where required. - See: * [Current list of Collaborators](./README.md#current-project-team-members) @@ -105,11 +101,9 @@ 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 reviewed -by the TSC by logging a GitHub issue. Any Collaborator, TSC member, or the -meeting chair can bring the issue to the TSC's attention by applying the -`tsc-review` label. If consensus-seeking among TSC members fails for a -particular issue, it may be added to the TSC meeting agenda by adding the +Any community member or contributor can ask that something be reviewed by the +TSC by logging a GitHub issue. If consensus-seeking among TSC members fails for +a particular issue, it may be added to the TSC meeting agenda by adding the `tsc-agenda` label. Prior to each TSC meeting, the meeting chair will share the agenda with |