-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta: Establishing the Moderation Team #329
Comments
@jasnell Can we move this issue to the Moderation repo? Since it is a jointly-owned repo, I think it makes more sense for this convo to exist there. |
Yeah that works too |
Can keep this here to send people to that repo for discussion from the TSC membership! |
Issue in moderation repo: https://github.com/nodejs/moderation/issues/128 |
Closing as the initial moderation team has been bootstrapped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@nodejs/community-committee, @nodejs/tsc, @nodejs/collaborators
PR #276 landed earlier today after long discussion.
Among other updates, the PR establishes a Moderation Team staffed by Collaborators approved by both the TSC and CommComm. The rules are spelled out fairly explicitly in the updated guidelines.
The Moderation Team is delegated authority for nearly all moderation actions. Both the CommComm and TSC has oversight over those actions.
I invite any Collaborator interested in helping with moderation as an official member of the Moderation Team to respond and leave a comment here self nominating.
The text was updated successfully, but these errors were encountered: