-
This was discussed in the roadmap for 2022, but didn't make the cut: #15383 Though it's becoming increasingly clear that there are some highly used projects in the ESLint community that are currently lacking a good home, being created by formerly active members of the community and now forked by other individual members to stay up to date. There has been an expressed desire to move some of these to a GitHub organization where they can be more collectively maintained, see eg. tise discussion in the According to @MichaelDeBoey there is interest from @xjamundx of moving And recently eg So – simple question from me is: Since there is already an idea to do this from the ESLint team itself it doesn't make sense to create a competing ESLint community organization. But when can the "official" one start to happen? As these modules all would get helped a lot by this happening sooner rather than later. If it won't happen soon, then we're better of creating an independent one. EDIT: @aladdin-add made a good clarification in mysticatea/eslint-plugin#29 (comment):
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 15 replies
-
In the interest of possibly allowing for other more non-ESLint generic JavaScript tools as well, I have sent out invites to yourself, @MichaelDeBoey and @aladdin-add to the @es-joy organization which I earlier set up as an umbrella org. to host such abandoned or unresponsive projects. Due to flakiness in my energy as a result of some health issues, I'd be happy to elevate someone with more energy to an organizer role, but to avoid chaos, I think we should keep the number of organizers to a minimum. |
Beta Was this translation helpful? Give feedback.
-
Although the @eslint-community org isn't meant to have the ESLint team maintain these packages, I would still like @nzakas to give access to some of us & connect us to @mysticatea so we can transfer his packages to the org & help maintaining them. |
Beta Was this translation helpful? Give feedback.
-
We would still like to do this, but we need a definition for what an eslint-community organization means. It is not intended to be a place where the ESLint team maintains unmaintained plugins…we don’t have the bandwidth to do that. It is intended to be a place where important community packages can live so that if the maintainers are unable to continue, then the ESLint team can step in and find a new maintainer. Unfortunately, we also have a lot of other higher priority work right now. If you are interested, the best course forward is to put together an RFC explaining what you envision the community to be, including which projects should be involved, what the criteria for acceptance should be, what permissions maintainers should have, what the role of the ESLint team should be, etc. |
Beta Was this translation helpful? Give feedback.
In the interest of possibly allowing for other more non-ESLint generic JavaScript tools as well, I have sent out invites to yourself, @MichaelDeBoey and @aladdin-add to the @es-joy organization which I earlier set up as an umbrella org. to host such abandoned or unresponsive projects.
Due to flakiness in my energy as a result of some health issues, I'd be happy to elevate someone with more energy to an organizer role, but to avoid chaos, I think we should keep the number of organizers to a minimum.