-
Notifications
You must be signed in to change notification settings - Fork 25
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 Next 10 Years team Meeting 2022-12-07 #181
Comments
I hope to be available but not 100% sure ! |
Attending today, as I wanted to talk about the doc proposal 🙈 |
Well, it would be good to have @mhdawson on the call 😅 but yea I think I could start the stream tbh. |
Let's then leave it for next week/or when Michael is back 👀 |
let's see if some people join maybe for like 5min and reschedule if not ? |
seems like @ovflowd and myself won't be able to attend - better to reschedule for next week |
I'll try to be there in case you end up rescheduling 😊 |
Time
UTC Wed 07-Dec-2022 15:00 (03:00 PM):
Or in your local time:
Links
Agenda
Extracted from next-10-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/next-10
Invited
*Next 10 years team: @nodejs/next-10
Observers/Guests
Notes
The agenda comes from issues labelled with
next-10-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/99950131676
For those who just want to watch: 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.
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
The text was updated successfully, but these errors were encountered: