Pride Month 2025

[github-actions]

The vote is now closed. The ballots are being counted.

This vote is open to all members of nodejs GitHub org. The vote will be open until 2025-05-28.
To make voting easier, the repository the vote is taking place is public,
which means the information of who participated to the vote will be public,
however what you voted for will only be accessible to TSC voting members.
TSC members shall not access the content of the ballots except to count
them once the vote has closed.

Refs: https://github.com/nodejs/moderation/issues/853

[ljharb]

There doesn't appear to be an option to change the logo regardless of IP address. What's the reason for that?

[avivkeller]

Isn't this what you are looking for?:

"Change the logo on the website (on pages where it appears today, i.e. not
on documentation pages), create a public lock issue asking folks that have
a problem with it to write to [email protected]."

[ronag]

Shouldn't we post about this vote on social media and the blog for visibility? I think less than a dozen of votes is not going to be representative...

[avivkeller]

I don't think this needs to be shared on social media, it's for org members only. @aduh95 posted it on Slack, but we can also tag @nodejs/collaborators

We have an "all-members" team, but it doesn't nearly contain all the members (maybe that should be changed?) looks like that's been fixed

[bjohansebas]

cc: @nodejs/all-members

[aduh95]

There doesn't appear to be an option to change the logo regardless of IP address. What's the reason for that?

Sounds a bit cryptic, is there any additional info about this? For example, my score might slightly differ if it would be implemented as "do only for selected list" or as "do except for selected list". 😅

Unfortunately, the list of possible candidates is final (amending it would invalidate the votes), I agree the wording could have been improved if we had gotten that feedback earlier. If someone wants to discuss on them, let's do that on #14 or in Slack to avoid sending notifications to hundreds of folks. The rule of thumbs is that if something's not mentioned, it won't be implemented (e.g. if #15 (comment) is the winning candidate, we wouldn't do any geofencing), and things that are not defined will be open for discussions (e.g. what IP filtering could be used is not defined, so we'd have to get consensus on some system if the winning candidate includes it).

[aduh95]

Last call for ballots, if you want to participate and haven't voted yet, please do so ASAP as the TSC will be closing it in a few hours.

[AugustinMauroy]

@aduh95 We can move forward to give the website team time to take action if necessary before June 1.

[bjohansebas]

@nodejs/tsc, please close the vote

[jasnell]

Just an update here... the vote was closed but due to a technical glitch we cannot actually unseal and tally the votes. Sigh. The TSC is discussing what next step to do.

[bmuenzenmeyer]

checking in on progress against the above - the thread I was a part of seemed to go dormant, so if there is something else brewing I'd love to hear it rather than take no action

[aduh95]

As James said above, we won't be able to recover the private key for this vote. In insight, a lot of things could have prevented it, but if you want a TL;DR for what happens, I've confused Math.min and Math.max in the part of the code in charge of picking how many TSC members should be necessary to rebuild the key; I'm sorry that silly mistake happened on the worst timing, the only thing left we can do is close this one and open a new vote: #17.