-
Notifications
You must be signed in to change notification settings - Fork 143
transfer https://github.com/watilde/remark-preset-lint-node/ into nodejs org #273
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
Comments
Relevant Node.js GitHub Organization Management Policy: https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANGEMENT_POLICY.md#repositories Code of conduct and CONTRIBUTING.md file would be good, but it's not currently called out as a requirement. #68 (which has not yet landed) includes them in a list of files that the repository should "ideally" contain, but again not a requirement. |
@watilde Whenever you like, you can initiate the transfer under Settings in the repo. (See https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/.) |
@Trott Sure! We also want to make sure about team access to transfer. Is that ok to make a team who manages release process? // As an example, I see |
No team + Add bots would also work fine probably! |
The team that owns We could add you to the Or we can create a new team as you suggest. Or we can add you and me and whoever else as individual owners. (All that with or without bots is fine by me too.) I'm technically not on TSC at the moment, so if someone else on @nodejs/tsc could handle setting up all the admin elements for the repo, that would be great. |
I did not know this, thank you! I'd like to follow this way.
Then I like this idea :)
|
Done 🎉 We can close this issue as resolved, thank you all :) Following up:
|
@nodejs/tsc Can someone please add @watilde to |
I think this can be closed now, but if I'm wrong, re-open. |
@apapirovski Could you make me Maintainer? I need to add |
Would seem to make sense to transfer https://github.com/watilde/remark-preset-lint-node/ into the nodejs org. (It was @watilde's idea: https://twitter.com/watilde/status/1062189105679716352. Good idea.)
Before it is transferred, it needs a code of conduct and a CONTRIBUTING.md file. Other than that, I think it's ready to go.
This is the remark-lint plugin with all of our settings for markdown linting.
@nodejs/tsc @nodejs/community-committee
The text was updated successfully, but these errors were encountered: