Skip to content

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

Closed
wants to merge 16 commits into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 6, 2025

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

  1. 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.

@mcollina
Copy link
Member

mcollina commented Aug 6, 2025

@aduh95 I can't seem to be able to push/vote:

Writing objects: 100% (5/5), 1.83 KiB | 1.83 MiB/s, done.
Total 5 (delta 3), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: error: GH013: Repository rule violations found for refs/heads/votes/b8ee8045-7abb-462f-820b-39005a588d68.
remote: Review all repository rules at https://github.com/nodejs/TSC/rules?ref=refs%2Fheads%2Fvotes%2Fb8ee8045-7abb-462f-820b-39005a588d68
remote:
remote: - Commits must have verified signatures.
remote:   Found 1 violation:
remote:
remote:   3ed3e5cfbf47d798554332ae2b0d911891088b33
remote:
To github.com:nodejs/TSC.git
 ! [remote rejected] HEAD -> votes/b8ee8045-7abb-462f-820b-39005a588d68 (push declined due to repository rule violations)
error: failed to push some refs to 'github.com:nodejs/TSC.git'
Error: git push,[email protected]:nodejs/TSC.git,HEAD:votes/b8ee8045-7abb-462f-820b-39005a588d68 failed: 1
    at ChildProcess.<anonymous> (file:///Users/matteo/.nvm/versions/node/v22.17.1/lib/node_modules/node-core-utils/node_modules/@node-core/caritat/dist/utils/runChildProcessAsync.js:32:27)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)

Note that 3ed3e5cfbf47d798554332ae2b0d911891088b33 is my commit.

@marco-ippolito

This comment was marked as resolved.

@benjamingr
Copy link
Member

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.

@mcollina
Copy link
Member

mcollina commented Aug 8, 2025

@benjamingr are you ok for being the one closing this?

@benjamingr
Copy link
Member

@mcollina

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.

We are still missing soe votes (or time) though?

@mcollina
Copy link
Member

mcollina commented Aug 8, 2025

yes

@jasnell
Copy link
Member

jasnell commented Aug 10, 2025

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.

@mcollina mcollina closed this Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.