Repository navigation
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-02-01 #65
Description
Activity
I won't be able to attend this week.
Here's a list of open issues labeled
ctc-review. If you are a CTC member, try to review them and comment (vote if appropriate) so that maybe we don't have to bring them to an actual meeting (although I see that some are already on the agenda for this week).Note: we will be voting to determine if Node wishes to ship an async or sync loader going forward. If anyone has questions prior to this, please feel free to send messages my way.
https://docs.google.com/presentation/d/1xZILfv5WeUBKyQ9s1w8zArNgzTMGRFQXyRseSskjcjw/view contains some notes and a brief overview will be held at the meeting.
Removing nodejs/node#10282. Feel free to re-add it if it needs CTC meeting time, but I don't think it does, at least not at this time.
Urgh, I take it back, we do need to figure out if we want to unlock the assert module or not. Adding it back.
My home internet connection is collateral damage after having PV cells installed so I'll probably miss this one. I'll comment/vote on the issues I have an opinion about.
Sorry, I will probably miss today.
- Restore copyright attribution node#10155, [WIP] meta: update copyright statements node#10599 — abstain until further notice (likely indefinitely), though on the second one I slightly dislike
All rights reserved.for the reasons noted in that PR. - assert: enforce type check in deepStrictEqual node#10282 — only
assert,module, andtimersareLocked. And there were minor and/or major changes in those recently (see API stability level «Locked» is inaccurate node#6528 for more details), so I think that the documentation is inaccurate there and differs from what is actually going on. TheStabledescription os more fit for all those. Note that we are planning a semver-minor level change for the modules resolution (ESM support) in the future — so it would be good if the module resolution mechanism stability contract stated something other than «only bugfixes» there. - deps: Add node-inspect node#10187 — abstain for this meeting.
- lib: be robust when process global is clobbered node#10135 — isn't updated yet afaik. Has to pass through CITGM and npm tests. I will take another look (on GitHub) once it gets updated.
- meta: deprecation policy node#7964 — LGTM and +1 on that.
- http: support environment-defined proxy node#8381 — abstain for this meeting.
- Restore copyright attribution node#10155, [WIP] meta: update copyright statements node#10599 — abstain until further notice (likely indefinitely), though on the second one I slightly dislike
Our largest viewer numbers ever:
Reacted by TwistedKap and Sakthipriyan Vairamani@bmeck after reading your slides, it looks like you found a way to preserve ordering with an async loader, which I thought we couldn't do initially, or am I making that up?
Also, sorry about my prior comment which I deleted, I saw the google link and assumed it was a spec and not slides. The slides were quite helpful and had all the necessary context.
- @mikeal initially we could not preserve order for a synchronous blocking loader. TC39 has a spec proposal that allows a sync loader if we need it. Async non-blocking always worked but you cannot return an object from requiring an ESM, CJS stays the way it is though. Async ESM would always need a Promise, so either require returns a Promise when ESM is the resolved dep, or we could throw on requiring ESM and tell people to use dynamic import as a function. On vavation so sorry I cant be of more use easily from my phone.…On Feb 6, 2017 7:21 PM, "Mikeal Rogers" ***@***.***> wrote: @bmeck <https://github.com/bmeck> after reading your slides, it looks like you found a way to preserve ordering with an async loader, which I thought we couldn't do initially, or am I making that up? Also, sorry about my prior comment which I deleted, I saw the google link and assumed it was a spec and not slides. The slides were quite helpful and had all the necessary context. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#65 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOUo5hkVEdklGA0pVH3uXnN0a_2S07Xks5rZ_88gaJpZM4LyLIA> .
Time
UTC Wed 01-Feb-2017 20:00 (08: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
nodejs/TSC
nodejs/node-eps
Invited
Notes
The agenda comes from issues labelled with
ctc-agendaacross 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.