You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the latest Node.js Release WG meeting we discussed the project health and the importance of leaving only active members with permissions for the threats evaluated by nodejs/TSC#1618.
Currently, we have a list of 11 releasers (in the README, and 10 with permissions https://github.com/orgs/nodejs/teams/releasers) but just a few of them are making releases this year. The idea is to finalize this task with a real active nodejs releasers list and seek new releasers if needed (possibly yes).
FWIW this discrepancy is because #1024 hasn't landed yet (but the teams have been updated). More specifically, I was keeping that open to track the offboarding checklist in #1024 (comment).
SGTM - this is somewhat worrisome. We should try to recruit more releasers (says somebody who has never done a Node.js release after being on the TSC for many years :/).
I've been a bit busy lately, but I had previously volunteered (#926) and that did not really move forward.
I am still happy to get involved and join the releasers team 🙂
@RafaelGSS "nodejs member", or collaborator? if it's still "collaborator" then indeed I don't qualify, but "member" is a very broad category that I've been included in for the better part of a decade.
SGTM - this is somewhat worrisome. We should try to recruit more releasers (says somebody who has never done a Node.js release after being on the TSC for many years :/).
I volunteer!
We already talked with @RafaelGSS and I've started attending meetings to get an idea of how things work, and I'll try to step up the contributions to hopefully get a Collaborator status soon
Activity
[-]@nodejs/releasers healthy[/-][+]@nodejs/releasers health[/+]richardlau commentedon Sep 25, 2024
FWIW this discrepancy is because #1024 hasn't landed yet (but the teams have been updated). More specifically, I was keeping that open to track the offboarding checklist in #1024 (comment).
Edit: landed now so the lists are in sync.
mcollina commentedon Sep 25, 2024
SGTM - this is somewhat worrisome. We should try to recruit more releasers (says somebody who has never done a Node.js release after being on the TSC for many years :/).
ljharb commentedon Sep 25, 2024
fwiw I'm still happy to be a releaser, if "not being a collaborator" stops being a barrier.
RafaelGSS commentedon Sep 25, 2024
Pinging the ones that are subject to be moved to emeritus:
If any of you would like to remain on the active list, please let me know! I'll proceed with this right after the next releasers meeting.
atlowChemi commentedon Sep 25, 2024
I've been a bit busy lately, but I had previously volunteered (#926) and that did not really move forward.
I am still happy to get involved and join the releasers team 🙂
ruyadorno commentedon Sep 27, 2024
@RafaelGSS Please leave me on the active list for now as I still plan to contribute whenever possible
juanarbol commentedon Sep 30, 2024
@RafaelGSS I would like to continue being a releaser.
RafaelGSS commentedon Sep 30, 2024
Looks like we won't have a Releasers meeting anytime soon. I'll proceed with off-boarding at the end of the week.
ljharb commentedon Oct 1, 2024
RafaelGSS commentedon Oct 1, 2024
Sorry I meant Node.js collaborator
doc: move releasers to emeritus
doc: move releasers to emeritus (#1044)
gurgunday commentedon Oct 17, 2024
I volunteer!
We already talked with @RafaelGSS and I've started attending meetings to get an idea of how things work, and I'll try to step up the contributions to hopefully get a Collaborator status soon
17 remaining items
doc: move releasers to emeritus (#1044)
RafaelGSS commentedon May 29, 2025
Closing as completed.