TSC meeting 01-February-2018

[eslint-deprecated]

Time

UTC Thu 01-Feb-2018 21:00:

• Los Angeles: Thu 01-Feb-2018 13:00
• Chicago: Thu 01-Feb-2018 15:00
• New York: Thu 01-Feb-2018 16:00
• Madrid: Thu 01-Feb-2018 22:00
• Moscow: Fri 02-Feb-2018 00:00
• Tokyo: Fri 02-Feb-2018 06:00
• Sydney: Fri 02-Feb-2018 08:00

Location

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

Agenda

Extracted from:

• Issues and pull requests from the ESLint organization with the "tsc agenda" label
• Comments on this issue

Invited

• Nicholas C. Zakas (@nzakas) - TSC
• alberto (@alberto) - TSC
• Kevin Partington (@platinumazure) - TSC
• Ilya Volodin (@ilyavolodin) - TSC
• Brandon Mills (@btmills) - TSC
• Toru Nagashima (@mysticatea) - TSC
• Gyandeep Singh (@gyandeeps) - TSC
• Kai Cataldo (@kaicataldo) - TSC
• Teddy Katz (@not-an-aardvark) - 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.

[not-an-aardvark]

Coyping over the agenda item from #71 (comment) because we didn't have time to discuss it at today's meeting:

I'd like to add one item to the agenda:

How are we doing on JSCS compatibility? Are we done yet? If not, what can we do to finish that off?

[not-an-aardvark]

Coyping over the agenda item from #71 (comment) because we didn't have time to discuss it at today's meeting:

And one more:

There was talk of possibly waiting on v5.0.0 until May when Node 4 hits end-of-life. As a TSC, should we agree to drop support for Node 4 in ESLint v5.0.0? If so, I think we should add a note or an issue to the v5.0.0 project.

[kaicataldo]

Agenda item:

I'd love to discuss if the team is at all interested in offering to maintain babel-eslint.

Some reasons why I'm suggesting this:

1. We already maintain typescript-eslint-parser
2. babel-eslint is a heavily relied on project in the JS community (having been downloaded almost 4M times in the last month)
3. babel-eslint is only used for ESLint, and has to track all changes we make. When we updated the parser API, the ESLint team ended up stepping in and making the changes necessary to make babel-eslint work (including running releases).
4. Most of the work for babel-eslint happens on the ESLint side of things, ensuring that the AST generated by Babylon is correct and that it works correctly with ESLint core.
5. The Babel team has had difficulty finding maintainers

I've spoken with @hzoo about this and it seemed like a worthwhile thing to at least investigate and discuss, regardless of the outcome.

[gyandeeps]

I wont be able to make it to this meeting since I am travelling.