Update the moderation policy to OpenJS escalation path, have TSC handle TSC reports#990
Merged
mcollina merged 6 commits intoJul 30, 2025
mainnodejs/admin:mainfrom
update-the-moderation-policy-to-openjs-escalation-pathnodejs/admin:update-the-moderation-policy-to-openjs-escalation-pathCopy head branch name to clipboard
Merged
Update the moderation policy to OpenJS escalation path, have TSC handle TSC reports#990mcollina merged 6 commits intomainnodejs/admin:mainfrom update-the-moderation-policy-to-openjs-escalation-pathnodejs/admin:update-the-moderation-policy-to-openjs-escalation-pathCopy head branch name to clipboard
mcollina merged 6 commits into
mainnodejs/admin:mainfrom
update-the-moderation-policy-to-openjs-escalation-pathnodejs/admin:update-the-moderation-policy-to-openjs-escalation-pathCopy head branch name to clipboard
Conversation
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Member
Author
|
cc @nodejs/tsc |
jasnell
reviewed
Jul 25, 2025
jasnell
approved these changes
Jul 25, 2025
Member
jasnell
left a comment
There was a problem hiding this comment.
One small suggestion. Otherwise LGTM
Co-authored-by: James M Snell <jasnell@gmail.com>
bmuenzenmeyer
approved these changes
Jul 25, 2025
benjamingr
approved these changes
Jul 25, 2025
benjamingr
reviewed
Jul 25, 2025
Co-authored-by: Benjamin Gruenbaum <benjamingr@gmail.com>
gireeshpunathil
approved these changes
Jul 25, 2025
jasnell
reviewed
Jul 25, 2025
joyeecheung
reviewed
Jul 25, 2025
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Member
Author
|
Adjusted to follow @tobie clarification in #990 (comment). |
joyeecheung
reviewed
Jul 27, 2025
tobie
reviewed
Jul 27, 2025
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Signed-off-by: Matteo Collina <hello@matteocollina.com>
Member
Author
|
I think this is ready. Please review. |
|
LGTM |
joyeecheung
approved these changes
Jul 30, 2025
Member
joyeecheung
left a comment
There was a problem hiding this comment.
LGTM. Thanks for opening openjs-foundation/cross-project-council#1522 - I think that captures what I noticed very well.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change updates the escalation path from an 8-year-old process defined in the Node.js Foundation era to what was agreed to when the OpenJS Foundation was established. We should have done it long ago, but we forgot to update this one.
I took the occasion to remove the
moderation-reviewlabel and directly upstream the problem of escalation to the OpenJS CoC Team. Alternatively, we could have an internal appeal process plus the OpenJS appeal process.I've also changed the verbiage to have the TSC self-moderate.
The current set of documents from OpenJS can be found at https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_POLICY.md#escalation.