-
Notifications
You must be signed in to change notification settings - Fork 133
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-03-27 #1521
Comments
@mcollina can you run the meeting? I have a non-movable conclit this week. Sorry for the late notice. We had agreed to spend most of the time discussing - nodejs/node#52107 |
I’ll be attending, I can start the stream etc. if needed. |
How are we doing? Someone hosting? |
are you still on the call? |
PR for minutes from @gireeshpunathil - #1523 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Time
UTC Wed 27-Mar-2024 15:00 (03: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/node
yarn
andpnpm
Corepack binaries by default #51886nodejs/nodejs.org
nodejs/TSC
nodejs/admin
nodejs/corepack
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: