Open Romick2005 opened 2 years ago
That would certainly be possible, but since this module is used in quite some projects I will have to be cautious about providing access to someone. My preference would be to partner up with a group or company that is active in the React Native scene.
@MichaelDeBoey would this qualify for @eslint-community as a backup?
My preference would be to partner up with a group or company that is active in the React Native scene.
I agree that would be best.
@Intellicode I think this repo qualifies to be transferred to the newly created official ESLint community org (@eslint-community).
We do have some acceptance criteria though. I think the best approach would be to write up for each criteria point why you think this repo is adhering it, so the community core team can decide if it would be a good idea to move this repo or not. As I see this personally, this would be just a formality for this repo, but having it in writing by the core maintainer, it would help us a lot when discussing if we want to include the plugin into the new org or not.
Bear in mind: we're not necessarily familiar with React Native, but 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.
You would still be the main maintainer, but it would (probably) be easier to attract new maintainers or at least minor upgrades are guaranteed by the community core team to keep this plugin working with latest ESLint versions.
@MichaelDeBoey Sorry for the late reply!
Thanks for your answer, I will consider writing up a proposal for being included in the community org, it looks like it could be a nice new home for this plugin!
@Intellicode can we get a pulse check on this?
If there would be any volunteers that would update and maintain this repository would be there any chances that @Intellicode give them some access to the code to keep this module alive?