Node.js Foundation Core Technical Committee (CTC) Meeting 2016-10-12

[Trott]

Time

UTC Wed 12-Oct-2016 16:00:

Timezone	Date/Time
US / Pacific	Wed 12-Oct-2016 09:00
US / Mountain	Wed 12-Oct-2016 10:00
US / Central	Wed 12-Oct-2016 11:00
US / Eastern	Wed 12-Oct-2016 12:00
Amsterdam	Wed 12-Oct-2016 18:00
Moscow	Wed 12-Oct-2016 19:00
Chennai	Wed 12-Oct-2016 21:30
Tokyo	Thu 13-Oct-2016 01:00
Sydney	Thu 13-Oct-2016 03:00

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/16l9D_OvAkeG6JoM_HRomHcFl--FTB61quvIWo9QfsVw
• Previous Minutes Google Doc: https://docs.google.com/document/d/1qRJiogKTWvxiHQ3S16MIR7BlynbXZPjqWwPScUSI2Rg

Agenda

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

nodejs/node

• governance: expand use of CTC issue tracker #8945
• doc: add supported platforms list #8922
• net: multiple listen() events fail silently #8419

nodejs/TSC

• Consider folding TSC into CTC #146

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)
• 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)
• Myles Borins @thealphanerd (CTC)
• Sakthipriyan Vairamani @thefourtheye (observer)
• 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]

Please note the change in time for this meeting! This meeting will be four hours earlier than our previous meetings. Check the time carefully.

This meeting will take place in slightly less than 36 hours from the time of this comment.

Stand up section is ready to go.

[MylesBorins]

I will be unable to attend this week as I will be observing Yom Kippur. Please let me know if you need my vote for anything

[joshgav]

I'll also not be able to attend this week. @Fishrock123 or @Trott could you take notes? Thanks!

[Trott]

I'll also not be able to attend this week. @Fishrock123 or @Trott could you take notes? Thanks!

I'm going to be facilitating the meeting so it would be great if someone else would volunteer to take notes. But if not, I will do my best!

[Fishrock123]

I would prefer not to be the one soley responsible for notes. I'm not very good at it and already running the livestream.

[joshgav]

@mhdawson - could you perhaps take notes this week? Thanks!

[MylesBorins]

It may be nice to discuss nodejs/nodejs.org#953

We currently don't have plans for the download page on the website when we have 3 release lines we are supporting

[addaleax]

I’ll really try to be there, but again there’s a good chance I’ll be late or won’t make it at all.

[rvagg]

I won't be at this one (unless I happen to wake up in the middle of the night and feel like listening in, unlikely!).

removed ctc-agenda from: doc: add supported platforms list #8922, it was covered last week and shouldn't need anything outside of GitHub for now (might come back for a v4.x version).

"net: multiple listen() events fail silently #8419" really just has that outstanding technical question - can a server close without Server#close() being called? If we can safely answer no to that then I don't think there's a blocker. In fact I don't think this even needs to be on the agenda at this stage.

"Consider folding TSC into CTC #146" is simply a discussion topic at this stage, we had a great chat about it last week at TSC and came up with some pros and cons and I'd like to hear what CTC has to say about it. Don't spend too much time down this rabbit hole if it's not productive though, it's not super urgent to decide anything.

Final thing, I'd like the CTC to be aware that we're migrating to a new nodejs.org / iojs.org / benchmarking.nodejs.org / dist.libuv.org backend server. Some of those are fronted by CloudFlare and we've already moved everything but nodejs.org to the new host. We're probably going to move nodejs.org tomorrow (today for some) if all seems to be going as planned. Please watch for any noise about things breaking, perhaps we've missed some use-case of the server or not transferred some key data that we've forgotten about. Let @jbergstroem or I know if anything comes up. IRC might be the best means of communication, even email, DM or other forms other than github @-mentions which are kind of flooded at the moment. Progress being tracked here: nodejs/build#516

[Fishrock123]

Livestream viewers, up to 8:

[jasnell]

oh dangit... totally forgot about the different time today! Need to get my calendar updated.

[mhdawson]

Minutes here: #9070