Node.js Foundation Core Technical Committee (CTC) Meeting 2017-01-04

[Trott]

Time

UTC Wed 04-Jan-2017 16:00:

Timezone	Date/Time
US / Pacific	Wed 04-Jan-2017 08:00
US / Mountain	Wed 04-Jan-2017 09:00
US / Central	Wed 04-Jan-2017 10:00
US / Eastern	Wed 04-Jan-2017 11:00
Amsterdam	Wed 04-Jan-2017 17:00
Moscow	Wed 04-Jan-2017 19:00
Chennai	Wed 04-Jan-2017 21:30
Tokyo	Thu 05-Jan-2017 01:00
Sydney	Thu 05-Jan-2017 03:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2017-01-04&iso=20170104T16
• or http://www.wolframalpha.com/input/?i=4pm+UTC%2C+Jan+04%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1ttXIoBjO-V9u6lb-c6PvvS4Au3AtnXu1AeWbV-mfKso/
• Previous Minutes Google Doc: https://docs.google.com/document/d/19-jajhdzTbO9RwOEKsZ74Lsw7Xx-uF41Nsx2LNdz0RI/

Agenda

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

nodejs/node

• Landing npm 4 into node 7 #10505
• console.log and util.format should support the %i integer conversion #10292
• timers: cleanup extraneous property on Immediates #10205
• [WIP] Restore copyright attribution #10155
• process: Add code to warnings, assign codes to deprecations #10116

nodejs/TSC

• Updating the Copyright #174

Invited

• Anna Henningsen @addaleax (CTC)
• Bradley Meck @bmeck (observer/GoDaddy/TC39)
• Ben Noordhuis @bnoordhuis (CTC)
• Сковорода Никита Андреевич @ChALkeR (CTC)
• Chris Dickinson @chrisdickinson (CTC)
• Colin Ihrig @cjihrig (CTC)
• Evan Lucas @evanlucas (CTC)
• Jeremiah Senkpiel @Fishrock123 (CTC)
• Tracy Hinds @hackygolucky (observer/Node.js Foundation)
• Fedor Indutny @indutny (CTC)
• James M Snell @jasnell (CTC)
• Josh Gavant @joshgav (observer/Microsoft)
• Michael Dawson @mhdawson (CTC)
• Julien Gilli @misterdjules (CTC)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Brian White @mscdex (CTC)
• Myles Borins @MylesBorins (CTC)
• Ali Ijaz Sheikh @ofrobots (CTC)
• Jenn Turner @renrutnnej (observer/Node.js Foundation)
• Rod Vagg @rvagg (CTC)
• Seth Thompson @s3ththompson (observer/Google)
• Shigeki Ohtsu @shigeki (CTC)
• Steven R Loomis @srl295 (observer/IBM/ICU)
• Michaël Zasso @targos (observer)
• Sakthipriyan Vairamani @thefourtheye (CTC)
• Trevor Norris @trevnorris (CTC)
• Rich Trott @Trott (CTC)

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]

Whoops, wrong local-time links in that original post. I've updated them above, but for those of you who might click them in email:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2017-01-04&iso=20170104T16
or http://www.wolframalpha.com/input/?i=4pm+UTC%2C+Jan+04%2C+2017+in+local+time

[Trott]

The timers issue on the agenda is (IMO at least) not really about timers but about a larger issue around managing semantic versioning and community expectations.

I put a summary (from my perspective, at least) at nodejs/node#10205 (comment). It's short. I would encourage people to read it (and @Fishrock123's comments above it) so as to have an informed discussion on Wednesday. (Even better, go and log your viewpoint on the topic in that GitHub issue and maybe we don't have to discuss it at the meeting at all. :-D )

[sam-github]

I don't think every internal (_ prefixed) symbol of every Node.js object needs to be treated as semver-major.

Technically, if it isn't part of the API, removing it is not semver-major.

Node.js is more cautious, because we don't want to break running code even if the code is relying on undocumented behaviour (for one, the docs aren't complete!).

But just because we try to be "better than semver", doesn't mean we must. If your code breaks because of this PR, I think you're on shaky ground complaining about it.

[Trott]

Tagged nodejs/node#10320 as ctc-agenda and hope we have time for it tomorrow.

[joshgav]

Notes: #57

[ChALkeR]

Sorry, it looks like I missed this one.