-
Notifications
You must be signed in to change notification settings - Fork 135
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
Moderation Team Certification #610
Comments
@nodejs/moderation |
I took the liberty of putting this on the Community Committee agenda, but obviously Community Committee folks should absolutely deal with this however they feel best. (Open an issue in their own repo? Do it asynchronously rather than at a meeting? Etc. etc.) |
I am fine with recommending that CommComm folks do it centrally here. AFAIK we've done this previously in nodejs/admin as the central "neutral" space for the committees' shared work, so perhaps moving this issue there might be a good idea... but I don't particularly think it matters. |
Moving this to the admin repo works for me. |
In CommComm was asked about moving to admin, so moved since there seemed to be agreement. |
CommComm voted on each member individually per the Moderation Policy guidelines, and each passed unanimously. |
We (along with @nodejs/community-committee) are supposed to certify Moderation Team folks every year. We didn't actually do it last year, if I'm not mistaken. Seems like doing it at the same time as the TSC Chair election will hopefully keep us from forgetting.
So, there's two things to do here: Figure out who of the current folks to re-certify for another year. And figure out if there's anyone not on the team now who could/should be added.
Current Moderation Team members:
The text was updated successfully, but these errors were encountered: