Commit 5897bf4
doc: edit "Involving the TSC"
Edit the "Involving the TSC" section of the Collaborator Guide to reduce
passive voice, make things concise, etc.
PR-URL: #26481
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Yuta Hiroto <hello@hiroppy.me>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent 78c4dbd commit 5897bf4
1 file changed
Lines changed: 3 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -374,13 +374,12 @@ deprecation level of an API. | |||
| 374 | 374 | ### Involving the TSC | |
| 375 | 375 | ||
| 376 | 376 | Collaborators may opt to elevate pull requests or issues to the [TSC][]. | |
| 377 | - This should be done where a pull request: | ||
| 377 | + Do this if a pull request or issue: | ||
| 378 | 378 | ||
| 379 | 379 | - is labeled `semver-major`, or | |
| 380 | 380 | - has a significant impact on the codebase, or | |
| 381 | - - is inherently controversial, or | ||
| 382 | - - has failed to reach consensus amongst the Collaborators who are | ||
| 383 | - actively participating in the discussion. | ||
| 381 | + - is controversial, or | ||
| 382 | + - is at an impasse among Collaborators who are participating in the discussion. | ||
| 384 | 383 | ||
| 385 | 384 | Assign the `tsc-review` label or @-mention the | |
| 386 | 385 | `@nodejs/tsc` GitHub team if you want to elevate an issue to the [TSC][]. | |
0 commit comments