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

docs: Remove mention of mailing list #16869

Merged
merged 5 commits into from Feb 14, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/src/contribute/governance.md
Expand Up @@ -78,6 +78,7 @@ A Committer who shows an above-average level of contribution to the project, par

1. Send email congratulating the new committer and confirming that they would like to accept. This should also outline the responsibilities of a committer with a link to the maintainer guide.
1. Add the GitHub user to the "ESLint Team" team
1. Add committer email to the ESLint team mailing list
1. Invite to Discord team channel
1. Tweet congratulations to the new committer from the ESLint Twitter account

Expand Down Expand Up @@ -144,8 +145,10 @@ A Reviewer is invited to become a TSC member by existing TSC members. A nominati
1. Set the GitHub user to be have the "Owner" role for the ESLint organization
1. Send a welcome email with a link to the [Maintain ESLint documentation](../maintain/) and instructions for npm 2FA.
1. Invite to the Discord TSC channel
1. Make the TSC member an admin on the ESLint team mailing list
1. Add the TSC member to the recurring TSC meeting event on Google Calendar
1. Add the TSC member as an admin to ESLint Twitter Account on Tweetdeck
1. Add the TSC member to the ESLint TSC mailing list as an "Owner"
1. Tweet congratulations to the new TSC member from the ESLint Twitter account

#### TSC Meetings
Expand Down
2 changes: 1 addition & 1 deletion docs/src/maintain/manage-issues.md
Expand Up @@ -24,7 +24,7 @@ There are four primary issue categories:
1. **Bug** - something isn't working the way it's expected to work.
1. **Enhancement** - a change to something that already exists. For instance, adding a new option to an existing rule or a bug in a rule where fixing it will result in the rule reporting more problems (in this case, use both "Bug" and "Enhancement").
1. **Feature** - adding something that doesn't already exist. For example, adding a new rule, new formatter, or new command line flag.
1. **Question** - an inquiry about how something works that won't result in a code change. We'd prefer if people use discussions or chatroom for questions, but sometimes they'll open an issue.
1. **Question** - an inquiry about how something works that won't result in a code change. We'd prefer if people use discussions or discord for questions, but sometimes they'll open an issue.
amareshsm marked this conversation as resolved.
Show resolved Hide resolved

The first goal when evaluating an issue is to determine which category the issue falls into.

Expand Down
2 changes: 1 addition & 1 deletion packages/eslint-config-eslint/README.md
Expand Up @@ -2,7 +2,7 @@

# ESLint Configuration

[Website](https://eslint.org) | [Configure ESLint](https://eslint.org/docs/latest/use/configure) | [Rules](https://eslint.org/docs/rules/) | [Contributing](https://eslint.org/docs/latest/contribute) | [Twitter](https://twitter.com/geteslint) | [Discord server](https://eslint.org/chat)
[Website](https://eslint.org) | [Configure ESLint](https://eslint.org/docs/latest/use/configure) | [Rules](https://eslint.org/docs/rules/) | [Contributing](https://eslint.org/docs/latest/contribute) | [Twitter](https://twitter.com/geteslint) | [Discord](https://eslint.org/chat) | [Mastodon](https://fosstodon.org/@eslint)

Contains the ESLint configuration used for projects maintained by the ESLint team.

Expand Down