-
-
Notifications
You must be signed in to change notification settings - Fork 140
jasnell nomination to the moderation team #1777
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
Conversation
@aduh95 I can't seem to be able to push/vote:
Note that |
This comment was marked as resolved.
This comment was marked as resolved.
Hey - not sure if late but I want to make the point James would be a good addition to the moderation team despite the objection(s). People who have raised issues with James being in the moderation team were concerned with James being involved with controversies or requiring self-moderation. I think this is something we can say about most people who have been in the project for a while. I fully trust James to know not to mix personal preferences or past grievances and be an impartial and objective moderator that brings a lot of context and experience to the table. I also trust James to recuse himself from discussions relating to issues where he has familiarity with the topic. While we don't always agree on everything we've always been able to collaborate effectively and reach an understanding. I also think it's important that there are certain individuals with the project and that the project works with that believe James "speaks for them" and trust him more than most of the existing moderation team to represent their interests in CoC reports. So for these reasons I am a strong +1 on James for the moderation team. |
@benjamingr are you ok for being the one closing this? |
We are still missing soe votes (or time) though? |
yes |
Given additional feedback I've received, I'm going to withdraw my self-nomination here. Sorry for the wasted effort. Hopefully others will step up and volunteer to help with moderation. The vote can be closed. |
The ballots from this vote should not be communicated publicly, as suggested in
#1773 (comment).
After the vote has been opened for seven days and/or all TSC voting members have
sent an encrypted ballot, the secret parts should be communicated to the
Moderation Team which would be charged to communnicate the result, while keeping
the ballots secret.
Refs: #1773 (comment)
Vote instructions:
To close the vote, at least 3 secret holder(s)1 must run the following command:
git node vote https://github.com/nodejs/TSC/pull/1777 --decrypt-key-part
/cc @nodejs/tsc
Current estimated participation: 70%
Footnotes
secret holders are folks who have access to the private key associated with a public key on hkps://keys.openpgp.org that references an email address listed on the TSC voting member list at the time of the opening of the vote. ↩