Node.js Foundation Core Technical Committee (CTC) Meeting 2017-06-28

[Trott]

Time

UTC Wed 28-Jun-2017 20:00 (08:00 PM):

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

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2017-06-28&iso=20170628T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+28%2C+2017+in+local+time

Links

• Minutes Google Doc: <>
• Previous Minutes Google Doc: https://docs.google.com/document/d/1W690JFykwVpN_V8zCSs_6yDTnFqAgE3juRz5k28SMWg

Agenda

Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

Invited

• Anna Henningsen @addaleax (CTC)
• Ben Noordhuis @bnoordhuis (CTC)
• Сковорода Никита Андреевич @ChALkeR (CTC)
• Colin Ihrig @cjihrig (CTC)
• Evan Lucas @evanlucas (CTC)
• Franziska Hinkelmann @fhinkel (CTC)
• Jeremiah Senkpiel @Fishrock123 (CTC)
• Fedor Indutny @indutny (CTC)
• James M Snell @jasnell (CTC)
• Joyee Cheung @joyeecheung (CTC)
• Matteo Collina @mcollina (CTC)
• Michael Dawson @mhdawson (CTC)
• Julien Gilli @misterdjules (CTC)
• Brian White @mscdex (CTC)
• Myles Borins @MylesBorins (CTC)
• Ali Ijaz Sheikh @ofrobots (CTC)
• Rod Vagg @rvagg (CTC)
• Shigeki Ohtsu @shigeki (CTC)
• Michaël Zasso @targos (CTC)
• Sakthipriyan Vairamani @thefourtheye (CTC)
• Trevor Norris @trevnorris (CTC)
• Rich Trott @Trott (CTC)

Observers

• Bradley Meck @bmeck (GoDaddy/TC39)
• Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
• Josh Gavant @joshgav (Microsoft)
• Mikeal Rogers @mikeal (Node.js Foundation Community Manager)
• Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
• Jenn Turner @renrutnnej (Node.js Foundation Newsletter Curator)

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]

No agenda items as of now. If you have something, leave a comment. Otherwise, likely to cancel again!

[Trott]

Items labeled for ctc-review; @nodejs/ctc please take a look:

• Invert dependency between core and readable-stream
• lib,src: exit process on unhandled promise rejection cleanup
• Confirmation that the stability definition is correct
• ~lib,src: eagerly exit process on unhanded promise rejections~~
• repl: make REPLServer.bufferedCommand private
• promises: more robust stringification

[bnoordhuis]

Removed the ctc-review label from issues that had it for > ~2 months and struck them through in Rich's comment.

[refack]

I don't think it's worth holding the meeting just for this, but there's an issue IMHO you should discuss (even next week): The semverity of changing messages in the new Errors.
There have been arguments pro and against marking message change as semver-major, but currently it seems like there is no explicit decision...
Ref: nodejs/node#13730 (comment) & nodejs/node#13730 (comment)
Ref2: nodejs/node#13834 (comment)

[mhdawson]

@refack does it make sense to open an issue specifically to discuss your question on messages/semver major and add ctc-review? That asks that CTC members weigh on the subject and then we can elevate to ctc-review if we don't see progress in the issue.

[refack]

@refack does it make sense to open an issue specifically to discuss your question on messages/semver major and add ctc-review? That asks that CTC members weigh on the subject and then we can elevate to ctc-review if we don't see progress in the issue.

Yes. On it.

[refack]

nodejs/node#13937 — meta: semver impact of Error messages

[Trott]

This sure seems like the meeting should be canceled. Closing, Feel free to comment or re-open if you think we should have the meeting.

[jasnell]

Interestingly... I think this would be the third CTC meeting in a row....