-
Notifications
You must be signed in to change notification settings - Fork 17
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 Loaders Team Meeting 2022-01-04 #57
Comments
I have a conflict at this time, can we move one hour later? |
Fine for me [to move it later] |
Okay, changing the time to 11 am PT / 2 pm ET / 19:00 UTC. I updated the initial post. There’s another team meeting at noon PT so we’ll have a hard stop. |
My home internet died this evening (and Holland is in lockdown), so I may not be able to attend 😞 |
I can use my company's office, so I can. |
We’re having technical issues and didn’t see @arcanis, so we’re rescheduling for next week at the same time (so 2022-01-11 at 11 am PT / 2 pm ET / 19:00 UTC). I updated the Node.js Google calendar so a new meeting issue should get autogenerated on Friday. |
Time
UTC Tue 04-Jan-2022 19:00 (07:00 PM):
Or in your local time:
Links
Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/loaders
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
loaders-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
link for participants: https://zoom.us/j/97506450082
For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live
The text was updated successfully, but these errors were encountered: