projects / pve-eslint.git / blame
| Commit | Line | Data |
|---|---|---|
| 8f9d1d4d DC |
1 | --- |
| 2 | title: Working Groups | |
| 3 | layout: doc | |
| 4 | ||
| 5 | --- | |
| eb39fafa DC |
6 | |
| 7 | The ESLint TSC may form working groups to focus on a specific area of the project. | |
| 8 | ||
| 9 | ## Creating a Working Group | |
| 10 | ||
| 11 | Working groups are created by sending an email to the team mailing list. Each working group: | |
| 12 | ||
| 13 | 1. Must have a GitHub team under the "ESLint Team" top-level GitHub team. (The GitHub team name should end with "WG" to distinguish it from other types of teams.) | |
| 14 | 1. Must have at least one TSC member. | |
| 15 | 1. May have any number of Committers and Reviewers. | |
| 16 | 1. Must have at least two members. | |
| 17 | ||
| 18 | Active working groups are listed on the [team page](https://eslint.org/team). | |
| 19 | ||
| 20 | ## How Working Groups Work | |
| 21 | ||
| 22 | Each working group is responsible for its own inner working. Working groups can decide how large or small they should be (so long as there is at least two members), when and who to add or remove from the working group, and how to accomplish their objectives. | |
| 23 | ||
| 24 | Working groups may be temporary or permanent. | |
| 25 | ||
| 26 | If working groups intend to make a significant change to the ESLint project, the proposal must still be approved by the TSC. |