TSC Meeting 10-November-2016

[nzakas]

Time

UTC Thu 10-Nov-2016 20:00:

• San Francisco: Thu 10-Nov-2016 13:00
• New York: Thu 10-Nov-2016 16:00
• Madrid: Thu 10-Nov-2016 22:00
• Moscow: Thu 10-Nov-2016 00:00
• Sydney: Fri 11-Nov-2016 08:00
• Tokyo: Fri 11-Nov-2016 06:00

Double check times here.

Location

https://gitter.im/eslint/tsc-meetings

Agenda

Extracted from "tsc agenda" labelled issues and pull requests from the ESLint org prior to the meeting and comments on this issue.

Invited

• Nicholas Zakas (@nzakas) - TSC
• Ilya Volodin (@ilyavolodin) - TSC
• Brandon Mills (@btmills) - TSC
• Gyandeep Singh (@gyandeeps) - TSC
• Toru Nagashima (@mysticatea) - TSC
• Alberto Rodríguez (@alberto) - TSC
• Kai Cataldo (@kaicataldo) - TSC

Public participation

Anyone is welcome to attend the meeting as observers. We ask that you refrain from interrupting the meeting once it begins and only participate if invited to do so.

[nzakas]

Agenda item: I'd like to spend some time talking about the issue/PR triaging process. It seems like we are really struggling to keep up with the incoming issues and PRs, and I'd like to talk through that a bit to see if we can figure out ways to improve the process.

[not-an-aardvark]

Agenda item: To what extent should ESLint's core rules account for syntax from custom parsers? We generally don't accept changes to rules that account for experimental JS features (e.g. eslint/eslint#7417), but we have accepted PRs that relate to type annotations (e.g. eslint/eslint#7445). Is there a general guideline for what features are supported by core rules?

[nzakas]

Agenda item: It looks like we're once again falling behind on merging PRs (I've seen some that have been open for more than a few days with zero comments). Let's talk about why that is.

[nzakas]

@not-an-aardvark we didn't discuss your question, but the answer is that there is a distinction between nonstandard ECMAScript features and ESTree features. For ECMAScript features, we only support things that are stage 4. For language extensions, such as JSX and type annotations, we try to support what is common and useful to our users. JSX is nonstandard, but was very highly requested, so we decided to make an exception there. There has also been a lot of asks around better Flow and TypeScript support, so we are supporting the ESTree type annotations extension, as both Flow and TypeScript benefit from that.