-
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 2024-07-31 #1603
Comments
Looks like a light agenda, but there is something to discuss. We can make it a short meeting if nothing else comes up. |
HeroDevs would like to take approximately 15 minutes (plus Q&A time) to go over the details of participation in the OpenJS ESP program, and get that moving forward. |
can I join the call re: swc deps / typescript / release to give a status update on concerns? |
Wdyt? |
@ChALkeR you are certainly welcome to join the call, given the light agenda it seems likely we'll have time to discuss the item you're bringing up |
PR for minutes - #1604 |
Time
UTC Wed 31-Jul-2024 14:00 (02: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/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: