-
Notifications
You must be signed in to change notification settings - Fork 137
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
Add step-by-step guide on transferring repos into the organization #68
Conversation
cc @nodejs/tsc @nodejs/community-committee |
* The purpose of the `nodejs-foundation` user is not to enable Build | ||
Workgroup members to publish npm modules, that should be left to the | ||
module collaborators. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might also can mention that developers should enable 2FA on npm as well here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@watilde The foundation account does not even enable 2FA on npm (can we fix that?) ...so probably not really worth mentioning that for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it's the same situation with @nodejs-github-bot
account without 2FA
in GitHub and collaborators need to enable their 2FA. We can mention later after landing this.
npm-management.md
Outdated
|
||
|
||
[`nodejs-foundation`]: https://www.npmjs.com/~nodejs-foundation | ||
[secrets repo]: https://github.com/nodejs/secrets/tree/master/test/test_credentials.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a dead link
Co-Authored-By: joyeecheung <joyeec9h3@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once the link is fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-Authored-By: joyeecheung <joyeec9h3@gmail.com>
Fixes: #63
The first commit moves the travis integration guide in nodejs/automation here.
The second commit moves the npm management documentation here.
The third commit adds a step-by-step guide on transferring repositories into the organization.
nodejs/TSC#495 (updating the repo management policy from "a simple majority is needed to transfer a repo" to "approval after 72 hours without objection") should land before this could land.
I can open PRs in the automation repo and the build repo to update the original docs with a pointer to the documents here after this lands.