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.

Sign up for GitHub

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

feat: create eslint-community GitHub organization #91

Merged
merged 10 commits into from
Aug 24, 2022
Merged

feat: create eslint-community GitHub organization #91

Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
2765132
feat: create "`@eslint-community` GitHub organisation" RFC
MichaelDeBoey May 31, 2022
cc49e34
Update README.md
MichaelDeBoey May 31, 2022
f8ce202
Update README.md
MichaelDeBoey Jun 1, 2022
535afc6
Update README.md
MichaelDeBoey Jun 2, 2022
bec2d70
Update README.md
MichaelDeBoey Jun 2, 2022
5046d59
Update README.md
MichaelDeBoey Jun 4, 2022
35bc00d
Update README.md
MichaelDeBoey Jun 16, 2022
7b6fa59
Update README.md
MichaelDeBoey Jun 24, 2022
89a5524
Update README.md
MichaelDeBoey Jul 15, 2022
ed9c14c
Update README.md
MichaelDeBoey Aug 6, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 8 additions & 15 deletions designs/2022-community-eslint-org/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,10 +71,10 @@ the updates would just resume).

Packages that are living under the new community org would be allowed to (keep)
accept(ing) sponsorship for the maintainers of that package.
If the community core team at some point decides to setup its own sponsorship
collective (like the core ESLint org has its
[Open Collective](https://opencollective.com/eslint)), packages could also
include this collective & the community org in their `FUNDING.yml`.
The community core team will also setup its own sponsorship collective (like the
MichaelDeBoey marked this conversation as resolved.
Show resolved Hide resolved
core ESLint org has its [Open Collective](https://opencollective.com/eslint)),
so packages should also include this collective & the community org in their
`FUNDING.yml`.

### Which projects should be involved?
MichaelDeBoey marked this conversation as resolved.
Show resolved Hide resolved

Expand Down Expand Up @@ -257,6 +257,10 @@ Examples of these kind of repos are:
live in the new org
<https://github.com/eslint/eslint-plugin-markdown>

As discussed in
[the ESLint TSC Meeting of July 14th, 2022](https://github.com/eslint/tsc-meetings/blob/main/notes/2022/2022-07-14-transcript.md),
the community core team will also be compensated out of the main ESLint budget.

## Documentation

<!--
Expand Down Expand Up @@ -349,7 +353,6 @@ package), people could still use the old package without any extra problems

- What exact acceptance criteria do we want to use?
MichaelDeBoey marked this conversation as resolved.
Show resolved Hide resolved
- What's the main place of communication for the community core team?
- Will the community core team be compensated out of the main ESLint budget?

## Help Needed

Expand All @@ -364,16 +367,6 @@ We would need to get access to the `@eslint-community` org & be brought in
contact with `@mysticatea` to transfer his repos to the new org & get `npm`
publish rights on these repos.

## Frequently Asked Questions

<!--
This section is optional but suggested.

Try to anticipate points of clarification that might be needed by
the people reviewing this RFC. Include those questions and answers
in this section.
-->

## Related Discussions

<!--
Expand Down