[pve-eslint.git] / eslint / docs / src / contribute / governance.md

---
title: Governance
eleventyNavigation:
    key: governance
    parent: contribute to eslint
    title: Governance
    order: 11

---

ESLint is an open source project that depends on contributions from the community. Anyone may contribute to the project at any time by submitting code, participating in discussions, making suggestions, or any other contribution they see fit. This document describes how various types of contributors work within the ESLint project.

## Roles and Responsibilities

### Users

Users are community members who have a need for the project. Anyone can be a User; there are no special requirements. Common User contributions include evangelizing the project (e.g., display a link on a website and raise awareness through word-of-mouth), informing developers of strengths and weaknesses from a new user perspective, or providing moral support (a "thank you" goes a long way).

Users who continue to engage with the project and its community will often become more and more involved. Such Users may find themselves becoming Contributors, as described in the next section.

### Contributors

Contributors are community members who contribute in concrete ways to the project, most often in the form of code and/or documentation. Anyone can become a Contributor, and contributions can take many forms. There is no expectation of commitment to the project, no specific skill requirements, and no selection process.

Contributors have read-only access to source code and so submit changes via pull requests. Contributor pull requests have their contribution reviewed and merged by a TSC member. TSC members and Committers work with Contributors to review their code and prepare it for merging.

As Contributors gain experience and familiarity with the project, their profile within, and commitment to, the community will increase. At some stage, they may find themselves being nominated as either a Website Team Member or Committer by an existing Website Team Member or Committer.

### Website Team Member

Website Team Members are community members who have shown that they are committed to the continued maintenance of [eslint.org](https://eslint.org/) through ongoing engagement with the community. Website Team Members are given push access to the `eslint.org` GitHub repository and must abide by the project's [Contribution Guidelines](../contribute/).

 Website Team Members:

* Are expected to work on public branches of the source repository and submit pull requests from that branch to the master branch.
* Are expected to delete their public branches when they are no longer necessary.
* Must submit pull requests for all changes.
* Have their work reviewed by Reviewers and TSC members before acceptance into the repository.
* May label and close website-related issues (see [Manage Issues](../maintain/manage-issues))
* May merge some pull requests (see [Review Pull Requests](../maintain/review-pull-requests))

To become a  Website Team Member:

* One must have shown a willingness and ability to participate in the maintenance of [eslint.org](https://eslint.org/) as a team player. Typically, a potential  Website Team Member will need to show that they have an understanding of the structure of the website and how it fits into the larger ESLint project's objectives and strategy.
* Website Team Members are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion.
* Have submitted a minimum of 10 website-related pull requests. What's a website-related pull request? One that is made to the `eslint.org` repository or the `docs` directory in the `eslint` repository and requires little effort to accept because it's well documented and tested.

New Website Team Members can be nominated by any existing Website Team Member or Committer. Once they have been nominated, there will be a vote by the TSC members.

It is important to recognize that membership on the website team is a privilege, not a right. That privilege must be earned and once earned it can be removed by the TSC members by a standard TSC motion. However, under normal circumstances Website Team Members remain for as long as they wish to continue engaging with the project.

### Committers

Committers are community members who have shown that they are committed to the continued development of the project through ongoing engagement with the community. Committers are given push access to the project's GitHub repos and must abide by the project's [Contribution Guidelines](../contribute/).

Committers:

* Are expected to work on public branches of the source repository and submit pull requests from that branch to the master branch.
* Are expected to delete their public branches when they are no longer necessary.
* Must submit pull requests for all changes.
* Have their work reviewed by TSC members before acceptance into the repository.
* May label and close issues (see [Manage Issues](../maintain/manage-issues))
* May merge some pull requests (see [Review Pull Requests](../maintain/review-pull-requests))

To become a Committer:

* One must have shown a willingness and ability to participate in the project as a team player. Typically, a potential Committer will need to show that they have an understanding of and alignment with the project, its objectives, and its strategy.
* Committers are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion.
* Have submitted a minimum of 10 qualifying pull requests. What's a qualifying pull request? One that carries significant technical weight and requires little effort to accept because it's well documented and tested.

New Committers can be nominated by any existing Committer. Once they have been nominated, there will be a vote by the TSC members.

It is important to recognize that committership is a privilege, not a right. That privilege must be earned and once earned it can be removed by the TSC members by a standard TSC motion. However, under normal circumstances committership exists for as long as the Committer wishes to continue engaging with the project.

A Committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become a reviewer, described below.

#### Process for Adding Committers

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

### Reviewers

Reviewers are community members who have contributed a significant amount of time to the project through triaging of issues, fixing bugs, implementing enhancements/features, and are trusted community leaders.

Reviewers may perform all of the duties of Committers, and also:

* May merge external pull requests for accepted issues upon reviewing and approving the changes.
* May merge their own pull requests once they have collected the feedback they deem necessary. (No pull request should be merged without at least one Committer/Reviewer/TSC member comment stating they've looked at the code.)

To become a Reviewer:

* Work in a helpful and collaborative way with the community.
* Have given good feedback on others' submissions and displayed an overall understanding of the code quality standards for the project.
* Commit to being a part of the community for the long-term.
* Have submitted a minimum of 50 qualifying pull requests.

A Committer is invited to become a Reviewer by existing Reviewers and TSC members. A nomination will result in discussion and then a decision by the TSC.

#### Process for Adding Reviewers

1. Add the GitHub user to the "ESLint Reviewers" GitHub team
1. Tweet congratulations to the new Reviewer from the ESLint Twitter account

### Technical Steering Committee (TSC)

The ESLint project is jointly governed by a Technical Steering Committee (TSC) which is responsible for high-level guidance of the project.

The TSC has final authority over this project including:

* Technical direction
* Project governance and process (including this policy)
* Contribution policy
* GitHub repository hosting

TSC seats are not time-limited. The size of the TSC can not be larger than five members. This size ensures adequate coverage of important areas of expertise balanced with the ability to make decisions efficiently.

The TSC may add additional members to the TSC by a standard TSC motion.

A TSC member may be removed from the TSC by voluntary resignation, by a standard TSC motion, or by missing four consecutive TSC meetings. In all cases, the TSC member will revert to Reviewer status unless they prefer Alumni status.

Changes to TSC membership should be posted in the agenda, and may be suggested as any other agenda item (see "TSC Meetings" below).

No more than 1/3 of the TSC members may be affiliated with the same employer. If removal or resignation of a TSC member, or a change of employment by a TSC member, creates a situation where more than 1/3 of the TSC membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more TSC members affiliated with the over-represented employer(s).

TSC members have additional responsibilities over and above those of a Reviewer. These responsibilities ensure the smooth running of the project. TSC members are expected to review code contributions, approve changes to this document, manage the copyrights within the project outputs, and attend regular TSC meetings.

TSC members may perform all of the duties of Reviewers, and also:

* May release new versions of all ESLint projects.
* May participate in TSC meetings.
* May propose budget items.
* May propose new ESLint projects.

There is no specific set of requirements or qualifications for TSC members beyond those that are expected of Reviewers.

A Reviewer is invited to become a TSC member by existing TSC members. A nomination will result in discussion and then a decision by the TSC.

#### Process for Adding TSC Members

1. Add the GitHub user to the "ESLint TSC" GitHub team
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

The TSC meets every other week in the TSC Meeting [Discord](https://eslint.org/chat) channel. The meeting is run by a designated moderator approved by the TSC.

Items are added to the TSC agenda which are considered contentious or
are modifications of governance, contribution policy, TSC membership,
or release process.

The intention of the agenda is not to approve or review all patches.
That should happen continuously on GitHub and be handled by the larger
group of Committers.

Any community member, Committer, or Reviewer can ask that something be added to
the next meeting's agenda by logging a GitHub Issue. Anyone can add the item to the agenda by adding
the "tsc agenda" tag to the issue.

Prior to each TSC meeting, the moderator will share the Agenda with
members of the TSC. TSC members can add any items they like to the
agenda at the beginning of each meeting. The moderator and the TSC
cannot veto or remove items.

No binding votes on TSC agenda items can take place without a quorum of
TSC members present in the meeting. Quorum is achieved when more than
half of the TSC members (minus non-attending members) are present.

The TSC may invite persons or representatives from certain projects to
participate in a non-voting capacity.

The moderator is responsible for summarizing the discussion of each
agenda item and sending it as a pull request after the meeting.

## Consensus Seeking Process

The TSC follows a
[Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
decision making model.

When an agenda item has appeared to reach a consensus, the moderator
will ask "Does anyone object?" as a final call for dissent from the
consensus.

If an agenda item cannot reach a consensus, a TSC member can call for
either a closing vote or a vote to table the issue to the next
meeting. The call for a vote must be approved by a majority of the TSC
or else the discussion will continue. Simple majority wins.

----

This work is a derivative of [YUI Contributor Model](https://github.com/yui/yui3/wiki/Contributor-Model) and the [Node.js Project Governance Model](https://github.com/nodejs/node/blob/master/GOVERNANCE.md).

This work is licensed under a [Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License](https://creativecommons.org/licenses/by-sa/2.0/uk/).
Commit	Line	Data
8f9d1d4d DC	1	---
8f9d1d4d DC	2	title: Governance
8f9d1d4d DC	3	eleventyNavigation:
8f9d1d4d DC	4	key: governance
f2a92ac6	5	parent: contribute to eslint
8f9d1d4d	6	title: Governance
f2a92ac6	7	order: 11
8f9d1d4d DC	8
8f9d1d4d DC	9	---
eb39fafa DC	10
	11	ESLint is an open source project that depends on contributions from the community. Anyone may contribute to the project at any time by submitting code, participating in discussions, making suggestions, or any other contribution they see fit. This document describes how various types of contributors work within the ESLint project.
	12
	13	## Roles and Responsibilities
	14
	15	### Users
	16
	17	Users are community members who have a need for the project. Anyone can be a User; there are no special requirements. Common User contributions include evangelizing the project (e.g., display a link on a website and raise awareness through word-of-mouth), informing developers of strengths and weaknesses from a new user perspective, or providing moral support (a "thank you" goes a long way).
	18
	19	Users who continue to engage with the project and its community will often become more and more involved. Such Users may find themselves becoming Contributors, as described in the next section.
	20
	21	### Contributors
	22
	23	Contributors are community members who contribute in concrete ways to the project, most often in the form of code and/or documentation. Anyone can become a Contributor, and contributions can take many forms. There is no expectation of commitment to the project, no specific skill requirements, and no selection process.
	24
	25	Contributors have read-only access to source code and so submit changes via pull requests. Contributor pull requests have their contribution reviewed and merged by a TSC member. TSC members and Committers work with Contributors to review their code and prepare it for merging.
	26
8f9d1d4d DC	27	As Contributors gain experience and familiarity with the project, their profile within, and commitment to, the community will increase. At some stage, they may find themselves being nominated as either a Website Team Member or Committer by an existing Website Team Member or Committer.
	28
	29	### Website Team Member
	30
f2a92ac6	31	Website Team Members are community members who have shown that they are committed to the continued maintenance of [eslint.org](https://eslint.org/) through ongoing engagement with the community. Website Team Members are given push access to the `eslint.org` GitHub repository and must abide by the project's [Contribution Guidelines](../contribute/).
8f9d1d4d DC	32
	33	Website Team Members:
	34
	35	* Are expected to work on public branches of the source repository and submit pull requests from that branch to the master branch.
	36	* Are expected to delete their public branches when they are no longer necessary.
	37	* Must submit pull requests for all changes.
	38	* Have their work reviewed by Reviewers and TSC members before acceptance into the repository.
f2a92ac6 DC	39	* May label and close website-related issues (see [Manage Issues](../maintain/manage-issues))
f2a92ac6 DC	40	* May merge some pull requests (see [Review Pull Requests](../maintain/review-pull-requests))
8f9d1d4d DC	41
	42	To become a Website Team Member:
	43
	44	* One must have shown a willingness and ability to participate in the maintenance of [eslint.org](https://eslint.org/) as a team player. Typically, a potential Website Team Member will need to show that they have an understanding of the structure of the website and how it fits into the larger ESLint project's objectives and strategy.
	45	* Website Team Members are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion.
	46	* Have submitted a minimum of 10 website-related pull requests. What's a website-related pull request? One that is made to the `eslint.org` repository or the `docs` directory in the `eslint` repository and requires little effort to accept because it's well documented and tested.
	47
	48	New Website Team Members can be nominated by any existing Website Team Member or Committer. Once they have been nominated, there will be a vote by the TSC members.
	49
	50	It is important to recognize that membership on the website team is a privilege, not a right. That privilege must be earned and once earned it can be removed by the TSC members by a standard TSC motion. However, under normal circumstances Website Team Members remain for as long as they wish to continue engaging with the project.
eb39fafa DC	51
	52	### Committers
	53
f2a92ac6	54	Committers are community members who have shown that they are committed to the continued development of the project through ongoing engagement with the community. Committers are given push access to the project's GitHub repos and must abide by the project's [Contribution Guidelines](../contribute/).
eb39fafa DC	55
	56	Committers:
	57
	58	* Are expected to work on public branches of the source repository and submit pull requests from that branch to the master branch.
	59	* Are expected to delete their public branches when they are no longer necessary.
	60	* Must submit pull requests for all changes.
	61	* Have their work reviewed by TSC members before acceptance into the repository.
f2a92ac6 DC	62	* May label and close issues (see [Manage Issues](../maintain/manage-issues))
f2a92ac6 DC	63	* May merge some pull requests (see [Review Pull Requests](../maintain/review-pull-requests))
eb39fafa DC	64
	65	To become a Committer:
	66
	67	* One must have shown a willingness and ability to participate in the project as a team player. Typically, a potential Committer will need to show that they have an understanding of and alignment with the project, its objectives, and its strategy.
	68	* Committers are expected to be respectful of every community member and to work collaboratively in the spirit of inclusion.
	69	* Have submitted a minimum of 10 qualifying pull requests. What's a qualifying pull request? One that carries significant technical weight and requires little effort to accept because it's well documented and tested.
	70
	71	New Committers can be nominated by any existing Committer. Once they have been nominated, there will be a vote by the TSC members.
	72
	73	It is important to recognize that committership is a privilege, not a right. That privilege must be earned and once earned it can be removed by the TSC members by a standard TSC motion. However, under normal circumstances committership exists for as long as the Committer wishes to continue engaging with the project.
	74
	75	A Committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become a reviewer, described below.
	76
	77	#### Process for Adding Committers
	78
	79	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.
	80	1. Add the GitHub user to the "ESLint Team" team
	81	1. Add committer email to the ESLint team mailing list
ebb53d86	82	1. Invite to Discord team channel
eb39fafa DC	83	1. Tweet congratulations to the new committer from the ESLint Twitter account
	84
	85	### Reviewers
	86
	87	Reviewers are community members who have contributed a significant amount of time to the project through triaging of issues, fixing bugs, implementing enhancements/features, and are trusted community leaders.
	88
	89	Reviewers may perform all of the duties of Committers, and also:
	90
	91	* May merge external pull requests for accepted issues upon reviewing and approving the changes.
	92	* May merge their own pull requests once they have collected the feedback they deem necessary. (No pull request should be merged without at least one Committer/Reviewer/TSC member comment stating they've looked at the code.)
	93
	94	To become a Reviewer:
	95
	96	* Work in a helpful and collaborative way with the community.
	97	* Have given good feedback on others' submissions and displayed an overall understanding of the code quality standards for the project.
	98	* Commit to being a part of the community for the long-term.
	99	* Have submitted a minimum of 50 qualifying pull requests.
	100
	101	A Committer is invited to become a Reviewer by existing Reviewers and TSC members. A nomination will result in discussion and then a decision by the TSC.
	102
	103	#### Process for Adding Reviewers
	104
	105	1. Add the GitHub user to the "ESLint Reviewers" GitHub team
	106	1. Tweet congratulations to the new Reviewer from the ESLint Twitter account
	107
	108	### Technical Steering Committee (TSC)
	109
	110	The ESLint project is jointly governed by a Technical Steering Committee (TSC) which is responsible for high-level guidance of the project.
	111
	112	The TSC has final authority over this project including:
	113
	114	* Technical direction
	115	* Project governance and process (including this policy)
	116	* Contribution policy
	117	* GitHub repository hosting
	118
	119	TSC seats are not time-limited. The size of the TSC can not be larger than five members. This size ensures adequate coverage of important areas of expertise balanced with the ability to make decisions efficiently.
	120
	121	The TSC may add additional members to the TSC by a standard TSC motion.
	122
	123	A TSC member may be removed from the TSC by voluntary resignation, by a standard TSC motion, or by missing four consecutive TSC meetings. In all cases, the TSC member will revert to Reviewer status unless they prefer Alumni status.
	124
	125	Changes to TSC membership should be posted in the agenda, and may be suggested as any other agenda item (see "TSC Meetings" below).
	126
	127	No more than 1/3 of the TSC members may be affiliated with the same employer. If removal or resignation of a TSC member, or a change of employment by a TSC member, creates a situation where more than 1/3 of the TSC membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more TSC members affiliated with the over-represented employer(s).
	128
	129	TSC members have additional responsibilities over and above those of a Reviewer. These responsibilities ensure the smooth running of the project. TSC members are expected to review code contributions, approve changes to this document, manage the copyrights within the project outputs, and attend regular TSC meetings.
	130
	131	TSC members may perform all of the duties of Reviewers, and also:
	132
	133	* May release new versions of all ESLint projects.
	134	* May participate in TSC meetings.
	135	* May propose budget items.
	136	* May propose new ESLint projects.
	137
	138	There is no specific set of requirements or qualifications for TSC members beyond those that are expected of Reviewers.
	139
	140	A Reviewer is invited to become a TSC member by existing TSC members. A nomination will result in discussion and then a decision by the TSC.
	141
	142	#### Process for Adding TSC Members
	143
	144	1. Add the GitHub user to the "ESLint TSC" GitHub team
	145	1. Set the GitHub user to be have the "Owner" role for the ESLint organization
f2a92ac6	146	1. Send a welcome email with a link to the [Maintain ESLint documentation](../maintain/) and instructions for npm 2FA.
ebb53d86	147	1. Invite to the Discord TSC channel
eb39fafa DC	148	1. Make the TSC member an admin on the ESLint team mailing list
	149	1. Add the TSC member to the recurring TSC meeting event on Google Calendar
	150	1. Add the TSC member as an admin to ESLint Twitter Account on Tweetdeck
	151	1. Add the TSC member to the ESLint TSC mailing list as an "Owner"
	152	1. Tweet congratulations to the new TSC member from the ESLint Twitter account
	153
	154	#### TSC Meetings
	155
ebb53d86	156	The TSC meets every other week in the TSC Meeting [Discord](https://eslint.org/chat) channel. The meeting is run by a designated moderator approved by the TSC.
eb39fafa DC	157
	158	Items are added to the TSC agenda which are considered contentious or
	159	are modifications of governance, contribution policy, TSC membership,
	160	or release process.
	161
	162	The intention of the agenda is not to approve or review all patches.
	163	That should happen continuously on GitHub and be handled by the larger
	164	group of Committers.
	165
	166	Any community member, Committer, or Reviewer can ask that something be added to
	167	the next meeting's agenda by logging a GitHub Issue. Anyone can add the item to the agenda by adding
	168	the "tsc agenda" tag to the issue.
	169
	170	Prior to each TSC meeting, the moderator will share the Agenda with
	171	members of the TSC. TSC members can add any items they like to the
	172	agenda at the beginning of each meeting. The moderator and the TSC
	173	cannot veto or remove items.
	174
	175	No binding votes on TSC agenda items can take place without a quorum of
	176	TSC members present in the meeting. Quorum is achieved when more than
	177	half of the TSC members (minus non-attending members) are present.
	178
	179	The TSC may invite persons or representatives from certain projects to
	180	participate in a non-voting capacity.
	181
	182	The moderator is responsible for summarizing the discussion of each
	183	agenda item and sending it as a pull request after the meeting.
	184
	185	## Consensus Seeking Process
	186
	187	The TSC follows a
	188	[Consensus Seeking](https://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
	189	decision making model.
	190
	191	When an agenda item has appeared to reach a consensus, the moderator
	192	will ask "Does anyone object?" as a final call for dissent from the
	193	consensus.
	194
	195	If an agenda item cannot reach a consensus, a TSC member can call for
	196	either a closing vote or a vote to table the issue to the next
	197	meeting. The call for a vote must be approved by a majority of the TSC
	198	or else the discussion will continue. Simple majority wins.
	199
	200	----
	201
	202	This work is a derivative of [YUI Contributor Model](https://github.com/yui/yui3/wiki/Contributor-Model) and the [Node.js Project Governance Model](https://github.com/nodejs/node/blob/master/GOVERNANCE.md).
	203
	204	This work is licensed under a [Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License](https://creativecommons.org/licenses/by-sa/2.0/uk/).