-
Notifications
You must be signed in to change notification settings - Fork 27
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-05-31 #138
Comments
Per discussion in nodejs/node-eps#49, I've changed it's label from |
Right now, we have no agenda items. The meeting is scheduled to take place in approximately 41 hours from now. If you have something that should be on the agenda, please suggest it soon! Thanks. Otherwise, it seems likely that the meeting will be canceled. |
Is this happening? |
Let’s call it off. (If it is happening, I’d be ~30 minutes late as always for this meeting time.) |
If there are no agenda items, then I think we can safely skip this week and give everyone the time back in their calendars. |
+1 to canceling. |
+1 to canceling |
Let's cancel. Any agenda items are far too late. |
I'm +1 as well. |
Okay, I’m closing this. Enjoy your extra hour. :) |
Time
UTC Wed 31-May-2017 16:00 (04:00 PM):
Or in your local time:
Links
Agenda
no agenda items
Invited
Notes
The agenda comes from issues labelled with
ctc-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
Uberconference; participants should have the link & numbers, contact me if you don't.
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.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the CTC that's not worth putting on as a separate agenda item, this is a good place for it.
The text was updated successfully, but these errors were encountered: