-
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
Reduce inactive collaborator duration #1540
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
03cddec
to
ffd5b7a
Compare
This comment was marked as resolved.
This comment was marked as resolved.
@aduh95 FYI The GPG I use on Github is with different email, and voting doesn't work because my email address is Sentry's in the TSC list. Additionally, lack of |
This comment was marked as resolved.
This comment was marked as resolved.
I voted from GitHub code spaces so it's unverified (I was just curious how am I supposed to use code spaces to push to a PR) |
I think I voted correctly |
This comment was marked as resolved.
This comment was marked as resolved.
FWIW the bot also thinks you voted correctly – otherwise it would show a red cross instead of a green tick next to your commit (and it would have posted a comment to notify you why the commit is rejected). I say think because it can't tell whether the encrypted data in your commit is valid YAML syntax. |
This comment was marked as resolved.
This comment was marked as resolved.
The command line didn’t work for me either but I was able to vote via the web: https://nodejs.github.io/caritat/#https://github.com/nodejs/TSC/pull/1540 |
I would like to close this vote, and for this effect, I'm revealing my key part:
|
I would like to close this vote, and for this effect, I'm revealing my key part:
|
@mcollina, @RafaelGSS, @richardlau: can one of you reveal his key part so the ballots can be decrypted? |
I would like to close this vote, and for this effect, I'm revealing my key part:
|
Election resultsSubject: Reduce inactive collaborator duration ResultsWinning candidate: Status quo: Keep the current inactive collaborator duration of 12 months Table of results
Voting dataParticipants:
Private key to decrypt ballots
Footnotes
|
@aduh95 Why does some votes have 1 or -1 on them and some of them has 1 or 0? |
@anonrig It's whatever people have voted (Tobias even voted 12 and 9, amusingly enough) |
How are such votes calculated? Would it be divided, so Tobias’ vote becomes 9/12 = 0.75 toward whichever option he preferred, rather than 1? Or is it just 12 > 9 so whichever option got 12 gets the full 1 vote? |
@GeoffreyBooth it's the latter, as written on the vote ballot, only the order matters. |
A nice improvement to the bot would be if the results comment could include the number and percentage of votes for each option. |
Currently, the bot looks through all commits on
main
that have landed in the last 12 months, and makes two lists:The bot will open a PR to move a collaborator to emeritus if they don't appear in either of those lists.
This vote is to decide whether we want to reduce the timespan from 12 months to
9 months.
Vote instructions:
git node vote https://github.com/nodejs/TSC/pull/1540
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/1540 --decrypt-key-part --post-comment
(N.B.: you should not add the--post-comment
flag if the token you're using does not have permission to post comments)/cc @nodejs/tsc
Current estimated participation: 100%
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. ↩