-
Notifications
You must be signed in to change notification settings - Fork 27
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-04-05 #93
Comments
At the request of @MylesBorins, adding Remove Legacy Debugger for 8.0.0 to the agenda. We now have one agenda item. But it's potentially a big one. (Hopefully not a ton of controversy, but lots of moving parts to catch up on.) |
It is possible that I will have to miss this weeks call as I will be on the way to San Francisco International on route to Barcelona. There are a number of items that will need to be discussed in relation to 8.0.0, however, so I will do my absolute best to join at least part of the call. |
It may help the Debugger discussion to review the notes from the last Diag WG meeting: |
I don't have much of a voice left so I don't think I'll be joining but I'm +1 on putting the old debugger out to pasture. |
I will be a little late. |
notes in #95 |
Time
UTC Wed 05-Apr-2017 20:00 (08:00 PM):
Or in your local time:
Links
Agenda
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: