-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
#93
Comments
I’d love to do this. @darcyclarke @nlf @jlamendo can anyone help with this? I don’t have permissions to move the repo. |
i can help with this today /cc @nzakas @MichaelDeBoey to my knowledge i need to be granted permissions to create a repo in the eslint-community org, if you can help with that @MichaelDeBoey i can get the transfer done. i would like to ask that i be kept as a maintainer on the repo after the transfer though! |
@nlf I invited you to the org. |
transfer is done! thank you for the help getting it moved, and for what i'm hoping is the first step in getting this plugin up to date and working more reliably |
Thanks all, glad to see this happen 🎉 |
@nlf Could you please also add |
It's up to you, but if you'd like, you're welcome to transfer this repository 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 @nzakas already asked for help in reviewing issues & PRs (see #76), I think this is a good candidate to transfer to the new org.
Again, totally up to you. I just want you to know we appreciate all you've done and you're welcome to join the organization if you like.
The text was updated successfully, but these errors were encountered: