Invitation to move to official `eslint-community` org
See original GitHub issueIt’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 https://github.com/nodesecurity/eslint-plugin-security/issues/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.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
@nzakas was already added, just added you and the bot though!
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