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

transfer https://github.com/watilde/remark-preset-lint-node/ into nodejs org #273

Closed
Trott opened this issue Nov 13, 2018 · 11 comments
Closed

Comments

@Trott
Copy link
Member

Trott commented Nov 13, 2018

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

@richardlau
Copy link
Member

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.

@Trott
Copy link
Member Author

Trott commented Nov 21, 2018

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

@watilde
Copy link
Member

watilde commented Nov 29, 2018

@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 citgm-admins, but do not see a team for core-validate-commit.

@watilde
Copy link
Member

watilde commented Nov 29, 2018

@Trott
Copy link
Member Author

Trott commented Nov 29, 2018

The team that owns core-validate-commit repo is @nodejs/automation.

We could add you to the @nodejs/linting team and make @nodejs/linting the owner of the repo.

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.

@watilde
Copy link
Member

watilde commented Nov 29, 2018

I did not know this, thank you! I'd like to follow this way.

The team that owns core-validate-commit repo is @nodejs/automation.

Then I like this idea :)

make @nodejs/linting the owner of the repo.

@watilde
Copy link
Member

watilde commented Nov 30, 2018

Done 🎉

We can close this issue as resolved, thank you all :)

Following up:

@Trott
Copy link
Member Author

Trott commented Nov 30, 2018

I assigned @nodejs/linting as committer. Could I join the team?

@nodejs/tsc Can someone please add @watilde to @nodejs/linting?

@apapirovski
Copy link
Member

@Trott @watilde Done

@Trott
Copy link
Member Author

Trott commented Nov 30, 2018

I think this can be closed now, but if I'm wrong, re-open.

@Trott Trott closed this as completed Nov 30, 2018
@watilde
Copy link
Member

watilde commented Dec 1, 2018

@apapirovski Could you make me Maintainer? I need to add @nodejs/bots to the repo and enable CI after that.

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

No branches or pull requests

4 participants