This repository was archived by the owner on Nov 9, 2017. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 27
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-29 #85
Labels
Comments
In addition to the three items that are on the agenda, @nodejs/ctc review is currently requested for these 12 (!!!) pull requests:
|
I won't be able to make it today. Can someone please take notes? Thanks! |
not going to make it today. v7.8 went out yesterday... expect lts rcs today |
Sorry, seems I had the time wrong in my calendar (10 PM instead of 6 PM.) |
Not too late to join now @bnoordhuis if you can. :-D |
PR for the minutes: #86 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Time
UTC Wed 29-Mar-2017 16:00 (04:00 PM):
Or in your local time:
Links
Agenda
Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
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: