Update the moderation policy to OpenJS escalation path, have TSC handle TSC reports#990
Uh oh!
There was an error while loading. Please reload this page.
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.