]> git.proxmox.com Git - pve-eslint.git/blame - eslint/docs/maintainer-guide/working-groups.md
bump version to 8.4.0-3
[pve-eslint.git] / eslint / docs / maintainer-guide / working-groups.md
CommitLineData
eb39fafa
DC
1# Working Groups
2
3The ESLint TSC may form working groups to focus on a specific area of the project.
4
5## Creating a Working Group
6
7Working groups are created by sending an email to the team mailing list. Each working group:
8
91. 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.)
101. Must have at least one TSC member.
111. May have any number of Committers and Reviewers.
121. Must have at least two members.
13
14Active working groups are listed on the [team page](https://eslint.org/team).
15
16## How Working Groups Work
17
18Each 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.
19
20Working groups may be temporary or permanent.
21
22If working groups intend to make a significant change to the ESLint project, the proposal must still be approved by the TSC.