Invitation to move to official `eslint-community` org

[jsx-eslint]

Invitation to move to official `eslint-community` org

[MichaelDeBoey]

I'm sorry, I thought it was, as you're the only one mentioned in sponsors & seems to be the only active person working on these repos.

Like I said before: it's totally up to you to join the official community org if you want to.

If you have any other concerns/questions/remarks, please let me know.

[MichaelDeBoey]

As I said: there's no separate ESLint community collective, so all new sources of funding would go to the main collective anyways.

[ljharb]

Thanks! I think anything that already has an org is probably ideal to remain there. I would hope that providing backup github/npm access to the community org's leadership would be sufficient to be considered "part of it", including funding, but that can be discussed separately.

[MichaelDeBoey]

I think anything that already has an org is probably ideal to remain there.

As seen in alternatives of the '@eslint-community GitHub organization' RFC, people still can have their own org if they want to.

The community could independently create multiple more focused organizations to maintain a subset of ESLint related packages.
Some examples of already existing organizations like that are @import-js (which maintains eslint-plugin-import), @jsx-eslint (which maintains eslint-plugin-jsx-a11y, eslint-plugin-react & jsx-ast-utils) & @standard (which maintains a couple of standard related ESLint configs)

I would hope that providing backup github/npm access to the community org's leadership would be sufficient to be considered "part of it"

If the repo isn't transferred, I don't think it's seen as 'part of the org', but like I said before: it's perfectly fine to have an org by yourself.
The idea behind my asking is because even though the packages are in an org, they're still reliant on you —@ljharb— for both GitHub & npm.
The new org wants to make sure these awesome ESLint related packages aren't completely lost if something would happen & you can't work on these projects anymore.

including funding

Packages can keep their sponsoring/funding if they want to.

Although packages that are living under the new community org would be allowed to (keep) accept(ing) sponsorship for the maintainer(s) of that package, they should also include the ESLint Open Collective & the ESLint org in their FUNDING.yml.

If you have any further questions, just ask away & I'll try to answer them as good as possible.

[ljharb]

They’re not reliant solely on me - all of them have multiple owners on github and npm.

[ljharb]

Thanks, I appreciate that!

If there were some kind of eslint-community github/npm account, i'd be happy to add them to reduce bus factor. In addition, funding is going to be something that eslint always has more of than the ecosystem, so it'd be great if the community is able to accumulate funds and distribute them, to projects in the org or not.

Sounds like I should close these issues for now, but happy to keep discussing.

[MichaelDeBoey]

If there were some kind of eslint-community github/npm account, i'd be happy to add them to reduce bus factor.

We currently recommend to add eslintbot on npm packages.
For GitHub there's only the org we now created, so if you don't want to transfer the repos, there's not really anything you can do except maybe adding ESLint TSC and/or community core members as well.

funding is going to be something that eslint always has more of than the ecosystem

As I said before: you can just keep your own funding on the repos if you want to, we're not telling people to remove it from their repos.

[ljharb]

Right, that's not what I mean - I'm saying that eslint's funding will have more money than our own funding whether we keep both or not, and it'd be nice to keep our own but still receive money from eslint-community.

[MichaelDeBoey]

If I'm correct, both @import-js & @jsx-eslint already get sponsored by the main ESLint Collective.
Since there's no separate ESLint community collective, but only the main collective, this wouldn't change a thing for you I think?

[ljharb]

Yes, at the moment that's the case. Perhaps I'm being overly optimistic about new sources of funding rolling in for the community :-)