TSC meeting 20-December-2018

[eslint-deprecated]

Time

UTC Thu 20-Dec-2018 21:00:

• Los Angeles: Thu 20-Dec-2018 13:00
• Chicago: Thu 20-Dec-2018 15:00
• New York: Thu 20-Dec-2018 16:00
• Madrid: Thu 20-Dec-2018 22:00
• Moscow: Fri 21-Dec-2018 00:00
• Tokyo: Fri 21-Dec-2018 06:00
• Sydney: Fri 21-Dec-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
• 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]

Copied from last meeting's agenda because that meeting was cancelled:

Agenda item: I'd like to nominate @g-plane as a committer.

[not-an-aardvark]

Copied from last meeting's agenda because that meeting was cancelled:

Agenda Item: I [@nzakas] would like to discuss how we can communicate better as a team. A few things:

1. I think we decided that nominations for committers and TSC would be done outside of the TSC meeting to avoid the pressure to go along with the nomination due to notes and transcript being public. We should come to a final agreement on this going forward.
2. I'd like to suggest that any change affecting the team should be sent to either the TSC or team mailing lists prior to the action being taken. This past weekend there was a bunch of rearranging of teams on the organization that triggered emails to people without any heads up. Also, issue templates were updated to automatically add labels, which broke the current workflow (see Triage label is no longer added to issues eslint-github-bot#99).
3. It seems like when emails are sent to any of the mailing lists, they don't receive many replies (if any). I'd like to understand why that is as I think the mailing lists are a much better way of making sure people see important information as opposed to Gitter, where it's easy to miss things.
4. I'm seeing a lot of PR comments beginning with "nit:" or "nitpick:" (not from anyone in particular, just in general), and I think these are counterproductive. I'd like to suggest that we shouldn't be nitpicking pull requests. Either a suggestion is important enough to be addressed, or it's not and we should ignore it.
5. Any other ideas for improving communication around important changes.

[nzakas]

I'm going to pull out some of my bullet points to see if we can resolve them on issues instead.

[nzakas]

Looks like I won’t be able to make it. The traveling has just taken too much out of me.

Is anyone else going to make it? (Would be good to get a count to see if there’s a quorum ahead of time.)

[not-an-aardvark]

I'm able to attend if the meeting is still on.

[kaicataldo]

I probably won't be able to make it today, unfortunately. Sorry for the short notice.