-
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-03-16 #1186
Comments
I can chair if somebody shares the password to start the streaming with me. |
This can be removed from the agenda. I've removed the tsc-agenda label from the issue. |
Daylight savings time has started in most of the U.S., much of Canada, and many other places. And it starts in much of Europe in about two weeks. So it's probably a good time for everyone on the TSC to confirm/update their availability in the availability spreadsheet. Send me an email if you need the link. @nodejs/tsc |
@brianwarner can you give @mcollina access to the zoom password? @mcollina I'm also adding you to the zoom email in case you need an authentication code.- nodejs/email#185 |
@mcollina thanks for chairing. |
@mcollina I've shared the creds with you. |
Unfortunately I had to reset my lastpass account - could you reshare? |
This can be taken off the agenda. |
Did the meeting time change for everyone because of DST in US? I'm surprised because I don't remember being ever invited at 12:00 |
Is there a meeting? It's 12 PM CET now. |
Startup performance updates:
|
I don't have creds to start the meeting... given the agenda, I suggest we cancel. |
I have, just a sec |
I'm currently having an argument with zoom, just a sec. |
Apparently I can't promote anyone as panelists. |
I suggest we cancel, the agenda is pretty light anyway. |
If you want we can use my zoom room or we can cancel. |
I'm ok with cancel. |
nodejs/node#40817 and #1176 can probably both be discussed in the respective issues first. +1 to cancel |
+1 about cancelling. |
I'm also okay with cancelling. |
+1 to cancel |
Canceled. However I would really like to understand why I couldn't promote anyone as panelist while being the host. |
Since it wasn't canceled until the start time, we should probably have minutes opened that doesn't do anything other than list the attendees. Gotta make sure we appease |
I (or anyone else) can open a minutes PR but I'd need to know who was there. I'm not sure how to collect those names other than maybe self-reporting. Any ideas? |
I was unable to promote anybody to the zoom, so technically there were no attendees. |
Goint to close since there was no meeting, no next step as far as I can tell. |
Time
UTC Wed 16-Mar-2022 11:00 (11:00 AM):
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
resume-ci
label to issues? #40817nodejs/TSC
Buffer
andEventEmitter
#1176Invited
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: