-
Notifications
You must be signed in to change notification settings - Fork 142
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
Create a nodejs npm organization? #545
Comments
cc @nodejs/tsc @nodejs/community-committee I think having an npm org so we can publish scoped packages is a good idea. https://www.npmjs.com/org/nodejs already exists. I don't know if it is owned by any of us or not though (it's not owned by the old nodejs-foundation user). If it's not owned, we need to send a request to npm to transfer ownership. |
@mmarchini afaik it is us. |
When we last discussed we went with using the There have been discussion over the years that maybe we should use the org feature (at the start is was not as well established), but I was not in the loop if |
Ah yeah, I remember that - I think the reason why we did this was to preserve the scope of |
As an extension of that: I don't think |
Agreed, but I don't think nodejs-foundation is an npm org, seems like it's a regular user: https://www.npmjs.com/~nodejs-foundation |
Correct, it is a regular user owned by the Build WG:
It's meant to be there as a backup to prevent us being locked out of any modules we own, e.g. due to users becoming inactive. |
On nodejs-foundation I think we talked about changing it but I think the agreement was that it was not worth the work required. If it had been an org that would have been different. |
We should transfer the |
@mmarchini in the i18n issue, it's noted that we own @nodejs/ and there's pushback on using it. ref: #505 |
I wouldn't say there is a lot of pushback. There are some questions and opinions on the matter and could be worth further discussing. |
Either way, we should transfer the nodejs org on npm to the nodejs-foundation account, regardless of how we're going to use it |
@ronag edited my phrasing 👍🏻 |
I think @ChALkeR owns |
@tniessen On npm? I don't. Also, +1 to the transfer idea. |
I am not sure who exactly own it but I can dig in. |
I'll submit a transfer request to npm using the nodejs-foundation account, that's probably the fastest way to find out and get it transferred |
I've already identified the owner and started the transfer request to my personal account (didn't think about transferring to foundation account) |
I'm an owner now! (also an owner of the @node scope)
So the next step is to add nodejs-foundation as an admin? |
I believe so, yeah |
@rvagg @mhdawson @jbergstroem y'all should've received an invite for the nodejs-foundation npm account to join the orgs above. The invite was sent to [email protected]. |
Can I get access? I would like to add readable-stream as well. |
I think it makes sense to add everyone from TSC (or everyone who wants to) as admins to the orgs (and maybe add it as part of our onboarding/offboarding) |
I got 3 invites in my email but they all lead to 404s. Maybe just let me know if I need to |
The links probably expired, or you need to be logged in as |
you can have multiple owners. I've escalated rvagg to also be an owner. There are still invites out for nodejs-foundation |
I can try to log in as nodejs-foundation a bit later to try to resolve that side of things. |
Still on my TODO list. |
I can do this tomorrow after the build infra onboarding. Also, for whoever ends up doin this, it's probably worth to coordinate with Myles via Slack so he can re-send the invite (suggesting Slack because real-time communication might make this easier). |
@mmarchini if you are going to do this let me know, otherwise I might try to schedule a time with Myles on Friday to do it. |
Got Myles to resend and the nodejs-foundation npm use is now a member of the node organisation. I terms of owners I think it makes sense for a number of TSC members (or all to be the owners). |
please add me |
please add me too :) |
I'm confused by the |
primarily based on #545 (comment) |
please add me too :) |
@mhdawson I misunderstood, I thought you meant to add more people to the nodejs-foundation org 😂 |
@MylesBorins there is no nodejs-foundation org. It is simply a user which we add as a backup to be able to add/manage collaborators on Node.js packages in case the other collaborators are no longer available. |
@mmarchini thanks for grabbing it. I think it should be likely be the TSC or subset as owners. |
@mhdawson was is your current up to date npm account? |
mhdawson1 |
I believe this can be closed? |
I think it might make sense to have a NodeJS organization on npm where different working groups could publish packages, e.g.
@nodejs/undici
,@nodejs/quic
etc... for feedback on new modules we are working on before or as an alternative to inclusion into core. I think this sometimes would be a preferable workflow to adding features as "experimental" (unless they depend on code in core).Would also be potentially useful for future packages we are working on in @nodejs/web-server-frameworks through e.g. #531.
The text was updated successfully, but these errors were encountered: