You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-05-10 #120
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.
Big agenda this week: 6 items. Are any of them things that have been resolved already and/or can otherwise be removed from the agenda or postponed to a later date?
Activity
Trott commentedon May 8, 2017
Big agenda this week: 6 items. Are any of them things that have been resolved already and/or can otherwise be removed from the agenda or postponed to a later date?
Trott commentedon May 8, 2017
Issues labeled
ctc-review. @nodejs/ctc PTAL:async_hooks initial implementationedit by @addaleax: practically superseded by Async Hooks - Initial Implementation node#12892GYPWGaddaleax commentedon May 8, 2017
nodejs/node#12442 should be quick, it just needs one more person of @bnoordhuis @fhinkel @Fishrock123 @mhdawson @rvagg @shigeki @trevnorris to vote in favour of or abstain in order for it to be accepted
(edit: done, we don’t need to bring this one up! 🎉)
refack commentedon May 8, 2017
Async Hooks - Initial Implementation is a continuation of
async_hooks initial implementation
IMHO Uniform way to trigger debugger on first line and regression: 3rd party debuggers are incompatible with node8 nighlies can be folded into inspector: restore --debug-brk alias as current consensus is nodejs/node#12630 (comment)
joshgav commentedon May 10, 2017
notes in #125