Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TSC meeting 18-July-2019 #141

Closed
eslint-deprecated bot opened this issue Jul 14, 2019 · 2 comments
Closed

TSC meeting 18-July-2019 #141

eslint-deprecated bot opened this issue Jul 14, 2019 · 2 comments

Comments

@eslint-deprecated
Copy link

Time

UTC Thu 18-Jul-2019 20:00:

  • Los Angeles: Thu 18-Jul-2019 13:00
  • Chicago: Thu 18-Jul-2019 15:00
  • New York: Thu 18-Jul-2019 16:00
  • Madrid: Thu 18-Jul-2019 22:00
  • Moscow: Thu 18-Jul-2019 23:00
  • Tokyo: Fri 19-Jul-2019 05:00
  • Sydney: Fri 19-Jul-2019 06: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

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.

@kaicataldo
Copy link
Member

kaicataldo commented Jul 14, 2019

Agenda item:

TSC Summary

It feels like a larger number of issues are getting closed with little or no discussion than we have had in the past. I think this is happening because the team is busier at the moment, but I'm worried that it makes it feel like we're ignoring proposals.

Generally, I think our process of auto-closing issues has worked well for us, but I do think it doesn't work as well when the team is busier.

TSC Questions:

  1. Is our current process working? Can we improve it?
  2. Can we make sure that we're at least leaving a comment kicking off a discussion when we add labels? I think removing the triage label before a team member comments can lead to nobody from the team commenting on it before it gets auto-closed.

@kaicataldo
Copy link
Member

Two more agenda items:

Adding these here since they're not in the main repo:

  1. Proposal for adding a build step archive-website#576
  2. Breaking: drop support for Node v6 eslint-scope#54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant