-
Notifications
You must be signed in to change notification settings - Fork 27
Official node.js npm account #26
Comments
+1 to an official npm organization (not individual account) |
I'm +1 on this too! |
+1 from me as well. Would be good to have the npm modules clearly associated with Node.js core. |
Looks like @chrisdickinson owns https://www.npmjs.com/~nodejs under his |
I'm totally for this. Think I brought this up a long time ago too. |
+1 from me. |
+1 |
@jbergstroem a few thoughts about how we might manage access to the credentials that will be needed to publish npms:
thoughts ? I am kind of leaning towards 2), but we'd still need somewhere to store the credentials in that case. |
I think the secrets repo is a perfect fit for this. We create a new folder and add gpg keys to people that should have access. I'm not super comfortable with leaning on Jenkins jobs for security, seeing how we get pretty serious vulnerabilities every other month. |
+1 to using the secrets repo. |
Discussion of how to manage here: nodejs/TSC#211 |
+1 |
I think we can probably close this now as covered in nodejs/TSC#211. I'll close and let me know if you disagree. |
Official projects such as citgm, nodereport, and readable-streams are currently published to npm using individual contributor accounts. If you look at the npm records there is no obvious official connection to the Node.js core project. It would likely be beneficial to have an official nodejs account on npm that can be associated with all official project.
The text was updated successfully, but these errors were encountered: