Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-04-05 #93

Closed
Trott opened this issue Apr 3, 2017 · 7 comments
Closed

Comments

@Trott
Copy link
Member

Trott commented Apr 3, 2017

Time

UTC Wed 05-Apr-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 05-Apr-2017 13:00 (01:00 PM)
US / Mountain Wed 05-Apr-2017 14:00 (02:00 PM)
US / Central Wed 05-Apr-2017 15:00 (03:00 PM)
US / Eastern Wed 05-Apr-2017 16:00 (04:00 PM)
Amsterdam Wed 05-Apr-2017 22:00 (10:00 PM)
Moscow Wed 05-Apr-2017 23:00 (11:00 PM)
Chennai Thu 06-Apr-2017 01:30 (01:30 AM)
Tokyo Thu 06-Apr-2017 05:00 (05:00 AM)
Sydney Thu 06-Apr-2017 06:00 (06:00 AM)

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.

@Trott
Copy link
Member Author

Trott commented Apr 3, 2017

Good news: No issues labeled ctc-agenda!

Bad news: 17 (!!!) issues labeled ctc-review! While we should certainly resolve as many of them as possible without elevating them to a meeting, maybe there are one or two particularly thorny issues that might benefit from putting on the agenda. (New error system proposed by @jasnell, I am looking in your direction!)

Additionally, I'm not sure if there are any final details or decisions that need to be reviewed/made related to debugger in 8.0.0. Paging @joshgav and @ofrobots.

Here are the ctc-review issues/PRs:

@Trott
Copy link
Member Author

Trott commented Apr 3, 2017

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.)

@jasnell
Copy link
Member

jasnell commented Apr 4, 2017

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.

@bnoordhuis
Copy link
Member

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.

@targos
Copy link
Member

targos commented Apr 5, 2017

I will be a little late.

@joshgav
Copy link
Contributor

joshgav commented Apr 5, 2017

notes in #95

@joshgav joshgav closed this as completed Apr 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants