Node.js Foundation Core Technical Committee (CTC) Meeting 2017-07-05

[Trott]

Time

UTC Wed 05-Jul-2017 11:00 (11:00 AM):

Timezone	Date/Time
US / Pacific	Wed 05-Jul-2017 04:00 (04:00 AM)
US / Mountain	Wed 05-Jul-2017 05:00 (05:00 AM)
US / Central	Wed 05-Jul-2017 06:00 (06:00 AM)
US / Eastern	Wed 05-Jul-2017 07:00 (07:00 AM)
Amsterdam	Wed 05-Jul-2017 13:00 (01:00 PM)
Moscow	Wed 05-Jul-2017 14:00 (02:00 PM)
Chennai	Wed 05-Jul-2017 16:30 (04:30 PM)
Hangzhou	Wed 05-Jul-2017 19:00 (07:00 PM)
Tokyo	Wed 05-Jul-2017 20:00 (08:00 PM)
Sydney	Wed 05-Jul-2017 21:00 (09:00 PM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2017-07-05&iso=20170705T11
• or http://www.wolframalpha.com/input/?i=11am+UTC%2C+Jul+05%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1uinCTY6zfxtuWmpPEYDcEnqFsEs17rPMlh1ujl_M8Ys/
• 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.

nodejs/node

• meta: semver impact of Error messages #13937

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

[ChALkeR]

@Trott Perhaps also bring attention to #152 at the meeting?

[Trott]

The only item currently on the agenda is meta: semver impact of Error messages.

Questions:

• I suggested in the issue that the determination (of whether these changes are or are not breaking changes) might best be delegated to the LTS group. If there's consensus about that, let's do that. Is there consensus about that?

• Is there a good chance we can get that resolved in the issue tracker? (Doesn't seem like it to me, but if the participants think otherwise, who am I to disagree?)

• If it is not likely to be resolved in the issue tracker any time soon, is the UTC 11:00 time for this meeting going to work for the participants? The participants are @mscdex, @mhdawson, @jasnell, and @mcollina. (@addaleax commented too but said she didn't have a strong opinion.)

[Trott]

@Trott Perhaps also bring attention to #152 at the meeting?

@ChALkeR Oh, yes, if we meet, let's be sure to at least bring that up during announcements. (Although I hope it's landed before then.)

[Trott]

Items labeled ctc-review; @nodejs/ctc PTAL:

• Invert dependency between core and readable-stream
• buffer: implement WHATWG Encoding Standard API
• repl: make REPLServer.bufferedCommand private
• promises: more robust stringification
• Request to move the Evangelism WG to CommComm
• src: adjust windows abort behavior to make sense

[addaleax]

I’d like to mention that at some point we might want to talk about #146 (V8 upgrades in 8.x) … maybe not this week, because we’re not going to actually do something before the security release anyway, but maybe the meeting after that.

[mscdex]

@Trott I won't be attending this meeting.

[Trott]

@Trott I won't be attending this meeting.

@mscdex Is that mostly because the time is a problem for you?

[mscdex]

@Trott Yes.

[Trott]

Looks like we're canceling this meeting and will discuss the error message vs. semver topic on the 21st 19th if it hasn't been resolved in GitHub by then. Does that sound about right? Looks like we'll also have the V8 upgrades in 8.x issue to talk about at that meeting too.