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 02-May-2024 #501

Closed
eslint-github-bot bot opened this issue Apr 22, 2024 · 2 comments · Fixed by #503
Closed

TSC meeting 02-May-2024 #501

eslint-github-bot bot opened this issue Apr 22, 2024 · 2 comments · Fixed by #503

Comments

@eslint-github-bot
Copy link

Time

UTC Thu 02-May-2024 20:00:

  • Los Angeles: Thu 02-May-2024 13:00
  • Chicago: Thu 02-May-2024 15:00
  • New York: Thu 02-May-2024 16:00
  • Madrid: Thu 02-May-2024 22:00
  • Moscow: Thu 02-May-2024 23:00
  • Tokyo: Fri 03-May-2024 05:00
  • Sydney: Fri 03-May-2024 06:00

Location

https://eslint.org/chat/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.

@nzakas
Copy link
Member

nzakas commented May 6, 2024

Agenda item:

It seems like RFCs are not getting reviewed in a timely fashion. The most recent was open for two weeks before any TSC member commented (me). We need to be paying more attention to these. I'd like to suggest that we have a formal "RFC duty" where we rotate through each week who is responsible for caretaking RFCs.

@nzakas
Copy link
Member

nzakas commented May 6, 2024

Agenda item:

Along the same lines, I'm finding that I need to re-ping the TSC multiple times on issues where I'm looking for feedback, sometimes over the course of multiple weeks. How can we tighten up the feedback loop?

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

Successfully merging a pull request may close this issue.

1 participant