Managing Issues

New issues are filed frequently, and how we respond to those issues directly affects the success of the project. Being part of the project team means helping to triage and address issues as they come in so the project can continue to run smoothly.

Things to Keep in Mind

Be nice. Even if the people are being rude or aggressive on an issue, as a project team member you must be the mature one in the conversation. Do your best to work with everyone no matter their style. Remember, poor wording choice can also be a sign of someone who doesn’t know English very well, so be sure to consider that when trying to determine the tone of someone’s message. Being rude, even when someone is being rude to you, reflects poorly on the team and the project as a whole.

Be inquisitive. Ask questions on the issue whenever something isn’t clear. Don’t assume you understand what’s being reported if there are details missing. Whenever you are unsure, it’s best to ask for more information.

Not all requests are equal. It’s unlikely we’ll be able to accommodate every request, so don’t be afraid to say that something doesn’t fit into the scope of the project or isn’t practical. It’s better to give such feedback if that’s the case.

Close when appropriate. Don’t be afraid to close issues that you don’t think will be done, or when it’s become clear from the conversation that there’s no further work to do. Issues can always be reopened if they are closed incorrectly, so feel free to close issues when appropriate. Just be sure to leave a comment explaining why the issue is being closed (if not closed by a commit).

Types of Issues

There are four primary issue categories:

Bug - something isn’t working the way it’s expected to work.

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”).

Feature - adding something that doesn’t already exist. For example, adding a new rule, new formatter, or new command line flag.

Question - an inquiry about how something works that won’t result in a code change. We’d prefer if people use the mailing list or chatroom for questions, but sometimes they’ll open an issue.

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

When an Issue is Opened

When an issue is opened, the bot will automatically apply the “triage” label. Issues labeled with “triage” are the ones that need to be looked at by team members to determine what to do next.

The steps for triaging an issue are:

Is it clear what is being requested?

No: add the “needs info” label to the issue. The bot will add a comment asking for more information. You don’t need to comment any further until the person who opened the issue responds with the information requested from the bot.

Yes:

Remove the “triage” label

Label questions with the “question” label

Label bug reports with the “bug” label (also use the “accepted” label if you can reproduce and verify the bug, otherwise add the “evaluating” label to indicate someone needs to verify)

Label requests for changes to existing features (new rule options, new configuration options, etc.) with the “enhancement” and “evaluating” labels

Label requests for completely new features (new rules, supporting a new file format, etc.) with the “feature” and “evaluating” labels

Use an appropriate label for the part of the project the issue refers to:

Questions: answer the question and close the issue when the conversation is over.

Bugs: if you can verify the bug, add the “accepted” label and ask if they would like to submit a pull request.

New Rules: if you are willing to champion the rule (meaning you believe it should be included in ESLint core and you will take ownership of the process for including it), add a comment saying you will champion the issue, assign the issue to yourself, and follow the guidelines below.

Rule Changes: if you are willing to champion the change and it would not be a breaking change (requiring a major version increment), add a comment saying that you will champion the issue, assign the issue to yourself, and follow the guidelines below.

Breaking Changes: if you suspect or can verify that a change would be breaking, label it as “Breaking”.

Duplicates: if you can verify the issue is a duplicate, add a comment mentioning the duplicate issue (such as, “Duplicate of #1234”) and close the issue.

Regardless of the above, always leave a comment. Don’t just add labels, engage with the person who opened the issue by asking a question (request more information if necessary) or stating your opinion of the issue. If it’s a verified bug, ask if the user would like to submit a pull request.

Note: “Good first issue” issues are intended to help new contributors feel welcome and empowered to make a contribution to ESLint. To ensure that new contributors are given a chance to work on these issues, issues labeled “good first issue” must be open for 30 days from the day the issue was labeled before a team member is permitted to work on them.

Accepting Issues

Issues may be labeled as “accepted” when the issue is:

A bug that you’ve been able to reproduce and verify (i.e. you’re sure it’s a bug)

A new rule or rule change that you’re championing and consensus has been reached for its inclusion in the project

The “accepted” label will be added to other issues by a TSC member if it’s appropriate for the roadmap.

Championing Issues

Guide the rule creation process until it’s complete (so only champion a rule that you have time to implement or help another contributor implement)

Once consensus has been reached on inclusion, add the “accepted” and, optionally, “help wanted” and “good first issue” labels, as necessary.

Consensus

Consensus is reached on issues when there are at least three team members who believe the change is a good idea and no one who believes the change is a bad idea. In order to indicate your support for an issue, leave a +1 reaction (thumbs up) on the original issue description in addition to any comments you might have.

When to Send to TSC

If consensus cannot be reached on an issue, or an issue’s progress has been stalled and it’s not clear if the issue should be closed, then you can refer the issue to the TSC for resolution. To do so, add the “tsc agenda” label to the issue and add a comment including the following information:

A one-paragraph summary of the discussion to this point.

The question you would like the TSC to answer.

The issue will be discussed at the next TSC meeting and the resolution will be posted back to the issue.

Evaluating Core Features and Enhancements (TSC members only)

In addition to the above, changes to the core (including CLI changes) that would result in a minor or major version release must be approved by the TSC by standard TSC motion. Add the label “tsc agenda” to the issue and it will be discussed at the next TSC meeting. In general, requests should meet the following criteria to be considered:

The feature or enhancement is in scope for the project and should be added to the roadmap

Someone is committed to including the change within the next year

There is reasonable certainty about who will do the work

When a suggestion is too ambitious or would take too much time to complete, it’s better not to accept the proposal. Stick to small, incremental changes and lay out a roadmap of where you’d like the project to go eventually. Don’t let the project get bogged down in big features that will take a long time to complete.

Breaking Changes: Be on the lookout for changes that would be breaking. Issues that represent breaking changes should be labeled as “breaking”.

When to Close an Issue

All team members are allowed to close issues depending on how the issue has been resolved.

Team members may close an issue immediately if:

The issue is a duplicate of an existing issue.

The issue is just a question and has been answered.

Team members may close an issue where the consensus is to not accept the issue after a waiting period (to ensure that other team members have a chance to review the issue before it is closed):

Wait 2 days if the issue was opened Monday through Friday.

Wait 3 days if the issue was opened on Saturday or Sunday.

In an effort to keep the issues backlog manageable, team members may also close an issue if the following conditions are met:

Unaccepted: Close after it has been open for 21 days, as these issues do not have enough support to move forward.

Accepted: Close after 90 days if no one from the team or the community is willing to step forward and own the work to complete to it.