TSC Meeting 29-Sep-2016

[nzakas]

Time

UTC Thu 15-Sep-2016 20:00:

• San Francisco: Thu 29-Sep-2016 13:00
• New York: Thu 29-Sep-2016 16:00
• Madrid: Thu 29-Sep-2016 22:00
• Moscow: Thu 29-Sep-2016 23:00
• Sydney: Fri 30-Sep-2016 06:00
• Tokyo: Fri 30-Sep-2016 05:00

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: Let's review how pull requests have been since removing the issue requirement.

[nzakas]

Agenda items:

• I'd like to nominate @not-an-aardvark as a committer.
• We should figure out who will be doing the next couple of releases.

[platinumazure]

Core roadmap: Should eslint/eslint#6874, eslint/eslint#6740, and/or eslint/eslint#6592 be added to the core roadmap project? (One might be too trivial, the others might be "help wanted" material.)

If this is resolved before the TSC meeting, I'll delete this.

Edit: Added "tsc agenda" label to relevant issues.

[nzakas]

@platinumazure if there are already issues/PRs open, please just add the label "tsc agenda" to those and include a comment that explains what you want the TSC to decide. (We reserve comments on this issue for things that aren't handled via issues in another repo.)

[platinumazure]

@nzakas My mistake, I thought that issue labels meant there was something about the issue proposal specifically that needed to be resolved.

[nzakas]

@platinumazure nope, "tsc agenda" is for any issue that needs a TSC discussion. That's why we ask you to add a comment with a summary of the issue and a question you'd like TSC to answer. We go through the list of all issues and PRs labeled with "tsc agenda" and respond during the meeting.