-
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 2022-09-14 #1283
Comments
I will chair this. |
Unfortunately, something came up on my end, and I won't be able to chair or attend :(. Sorry folks. |
I can’t attend either. The two items on our agenda feel like they can both be resolved async, if people could vote on those issues if they haven’t already?
Since we only have one confirmed attendee for this meeting, perhaps it’s best to cancel and we can tackle either of these agenda items next week if they’re not resolved async by then? |
Let's cancel. Any objections? |
Closing since it sounds like the meeting was cancelled. |
Time
UTC Wed 14-Sep-2022 12:00 (12: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
nodejs/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: