-
-
Notifications
You must be signed in to change notification settings - Fork 138
Node.js Technical Steering Committee (TSC) Meeting 2022-05-18 #1228
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I'll be able to attend this one but I'll have to leave at UTC 3:30pm. |
I'm traveling this week and I won't be able to join. |
@nodejs/tsc there are still a few people who have not voted on #1224. Please vote even you just want to abstain. |
Please vote especially if you want to abstain. Registering an abstention vote is an easy decision and it helps us get to a conclusion faster. It also leaves the decision in the hands of the people who have strong opinions and are (hopefully) highly informed. |
I have a conflict but will try to join for the first half. |
PR for minutes - #1229 |
Time
UTC Wed 18-May-2022 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
fetch
breakssource-map
#42638nodejs/TSC
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: