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

Maintainers wanted! #323

Open
Romick2005 opened this issue Sep 20, 2022 · 5 comments
Open

Maintainers wanted! #323

Romick2005 opened this issue Sep 20, 2022 · 5 comments

Comments

@Romick2005
Copy link

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?

@Intellicode
Copy link
Owner

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.

@bmish
Copy link

bmish commented Oct 11, 2022

@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.

@MichaelDeBoey
Copy link

MichaelDeBoey commented Oct 11, 2022

@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.

@Intellicode
Copy link
Owner

@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!

@FilDevTronic
Copy link

@Intellicode can we get a pulse check on this?

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

5 participants