Skip to content
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

@nodejs/releasers health #1036

Open
RafaelGSS opened this issue Sep 19, 2024 · 10 comments
Open

@nodejs/releasers health #1036

RafaelGSS opened this issue Sep 19, 2024 · 10 comments

Comments

@RafaelGSS
Copy link
Member

RafaelGSS commented Sep 19, 2024

Hi folks,

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

This is the list of 2024 releases: https://github.com/RafaelGSS/nodejs-stats/blob/main/releases/2024-releases.csv.

Releasers:

  • RafaelGSS
  • Marco Ippolito
  • Richard Lau
  • Antoine du Hamel
  • Michaël Zasso
  • Ulises Gascón

cc: @nodejs/releasers

@marco-ippolito marco-ippolito changed the title @nodejs/releasers healthy @nodejs/releasers health Sep 19, 2024
@richardlau
Copy link
Member

richardlau commented Sep 25, 2024

Currently, we have a list of 11 releasers (in the README, and 10 with permissions https://github.com/orgs/nodejs/teams/releasers)

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
Copy link
Member

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
Copy link
Member

ljharb commented Sep 25, 2024

fwiw I'm still happy to be a releaser, if "not being a collaborator" stops being a barrier.

@RafaelGSS
Copy link
Member Author

RafaelGSS commented 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
Copy link
Member

We should try to recruit more releasers

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
Copy link
Member

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.

@RafaelGSS Please leave me on the active list for now as I still plan to contribute whenever possible

@juanarbol
Copy link
Member

@RafaelGSS I would like to continue being a releaser.

@RafaelGSS
Copy link
Member Author

Looks like we won't have a Releasers meeting anytime soon. I'll proceed with off-boarding at the end of the week.

  • @atlowChemi feel free to start joining our meetings and following our discussions on this repo
  • @ljharb last time our team discussed it, it's mandatory to be a nodejs member in order to be a releaser.

@ljharb

This comment was marked as resolved.

@RafaelGSS
Copy link
Member Author

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

Sorry I meant Node.js collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants