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

Invitation to move to official eslint-community org #297

Closed
MichaelDeBoey opened this issue Sep 10, 2022 · 6 comments
Closed

Invitation to move to official eslint-community org #297

MichaelDeBoey opened this issue Sep 10, 2022 · 6 comments

Comments

@MichaelDeBoey
Copy link
Member

MichaelDeBoey commented Sep 10, 2022

We would love to have this repo added to the official @eslint-community organization on GitHub.

As you can read in the '@eslint-community GitHub organization' RFC, the goal of this new org is to have a place where community members can help ensure widely depended upon ESLint related packages stay up to date with newer ESLint releases and doesn't hold the wider community back without depending on one person's GitHub/npm account.

Since this plugin is (together with eslint-plugin-node) a recommended plugin for linting custom plugins & since you —@not-an-aardvark— (according to eslint/rfcs#91 (comment)) already discussed with @aladdin-add to transfer this repo to a better home, you're welcome to transfer this repository to the new org.

@not-an-aardvark
Copy link
Contributor

Thanks. It looks like I don't have permission to transfer this repository to @eslint-community because I'm not allowed to create public repositories in that organization. Seems like there are a few possible workarounds:

  • Temporarily adding me as a member to @eslint-community so that I could move the repo there. I would transfer the repository and then leave the organization (since I haven't really been involved in maintaining the plugin recently)
  • I could transfer the repository to another person who has the ability to create repositories in @eslint-community, and then that person would subsequently transfer the repository to @eslint-community. (@MichaelDeBoey, not sure if that would be you or someone else -- currently @eslint-community has no public members, but I can't tell if you're a private member.)

@MichaelDeBoey
Copy link
Member Author

@not-an-aardvark I've created a team with you (& @aladdin-add?) for this repo & invite you

@not-an-aardvark
Copy link
Contributor

I've transferred the repository. Thanks for getting eslint-community set up!

Let me know if there's anything else I should do. From skimming this, it seems like I should add @eslintbot as an owner to the NPM package?

@MichaelDeBoey
Copy link
Member Author

I think it would be good to add both @eslintbot, myself (@michaeldeboey) & @nzakas

@not-an-aardvark
Copy link
Contributor

Ok, I've added those three accounts.

@MichaelDeBoey
Copy link
Member Author

Probably also a good idea to add the eslint-community npm org

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

2 participants