-
Notifications
You must be signed in to change notification settings - Fork 134
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
Node.js Technical Steering Committee (TSC) Meeting 2023-07-26 #1419
Comments
I plan to chair this |
I think nodejs/node#48890 should also be on the agenda, it looks like Moshe added the label after the issue was generated. |
In case I don't make it to the meeting, here is something from the CPC meeting that can go either in the announcements or in the CPC update:
|
I can’t attend and Moshe is 😕 so maybe it’s better to discuss next week? It’s also unclear what the ask of the TSC is here; the comment just says “This seems like the kind of thing the TSC should have an opinion on.” |
I will miss the first half due to a double booking. |
Time
UTC Wed 26-Jul-2023 13:00 (01:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/TSC
nodejs/admin
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: