Node.js Foundation Core Technical Committee (CTC) Meeting 2016-09-07

[Trott]

Time

UTC Wed 07-Sep-2016 20:00:

Timezone	Date/Time
US / Pacific	Wed 07-Sep-2016 13:00
US / Mountain	Wed 07-Sep-2016 14:00
US / Central	Wed 07-Sep-2016 15:00
US / Eastern	Wed 07-Sep-2016 16:00
Amsterdam	Wed 07-Sep-2016 22:00
Berlin	Wed 07-Sep-2016 22:00
Moscow	Wed 07-Sep-2016 23:00
Tokyo	Thu 08-Sep-2016 05:00
Sydney	Thu 08-Sep-2016 06:00

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1GRgBC5Dv5luqlRc6egtxmkrQULJXa3M3CqGqWfoogV8
• Previous Minutes Google Doc: https://docs.google.com/document/d/1qYUOfiiytaZ0-YZVZ1NZX9O-4SE28QNooapOdcjlPqA

Agenda

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

nodejs/node

• Process for determining supported platforms #8265
• src: add no-op for --harmony-proxies flag #8395

nodejs/node-eps

• AsyncWrap public API proposal #18

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

This meeting will take place 26 hours from now.

Standup section of doc is ready to go. @nodejs/ctc

[MylesBorins]

Introduce staging branch for stable release streams #6306

it appeared that this was voted on in the last meeting based on the notes. Should we remove it from agenda?

[cjihrig]

I'm going to have to miss again. Hoping to be back before the end of the month.

[addaleax]

The agenda isn’t, like, huge, so maybe we could have a quick talk about #8395 (no-ops for the removed harmony flags)?

[Trott]

@addaleax I've added that to the agenda. I imagine you want to get consensus on how to deal with V8 flags that disappear, and not necessarily on that specific PR. Please correct me if I'm wrong and/or be prepared to frame the conversation at the meeting tomorrow.

I suspect this comment from @jasnell is a good summary of what we might want to discuss (and maybe even vote on if we can't get consensus):

I would definitely be in favor of making these noops when they disappear from v8 in patch or minor releases, and removing them entirely in majors. I would prefer that a deprecation warning be printed but I'm ok with simply ignoring them.

[addaleax]

Thanks! And, yeah, it’s not about that specific PR, and not necessarily about a solution this week, it’s just something that seems to me like it might benefit from a bit of synchronous discussion if we have the time.

[Trott]

For this issue:

• Process for determining supported platforms #8265

The outcome of last week's discussion was:

• Build WG will prepare initial list of supported platforms in their next meeting.
• Then CTC will review and decide next steps.

I imagine that first bullet point may not be quick and easy, but just in case: Did @nodejs/build pull that information together? And if so, is it somewhere that I can include a link to it and others can review it ahead of the meeting?

/cc @rvagg

[jasnell]

I will be able to join for the first 30 minutes of the call. After that I'll be helping out with my youngest son's after school robotics club for a bit so... yeah, priorities 😜

[Trott]

@jasnell You probably picked a good week for it. The agenda is pretty small and perhaps about to get smaller.

[Trott]

I believe we can remove this item from the agenda:

• Move ecosystem detection tool to nodejs org #7935

The outcome from last week was:

• Prep repo for migration.
• Open issue in nodejs/tsc.

I'm not sure if that would be something @ChALkeR or @cjihrig would do, but I imagine it can be done by anyone with the interest in doing it.

I'm going to remove ctc-agenda from that issue and remove it from this week's agenda. If this is an error on my part, please re-add the label, edit the agenda, and/or comment here. Thanks!

[Trott]

The result of this item from last week:

• AsyncWrap public API proposal #18

was this:

• Trevor to update all code and ask for vote on specific item(s).

@trevnorris Is that done or likely to be done before the meeting? If so, can you drop a link here? If it's ready to go, we'll do that first since it's the most actionable thing on the agenda right now. If it's not ready to go, then I imagine we're likely to table it until next week?

[rvagg]

@Trott no, build didn't get a chance to do that list yet, I'm going to remove ctc-agenda from that issue for now, we haven't even had a chance to have a build WG meeting since last week (we do it every 3 weeks, next is the 20th).

[rvagg]

For those wanting to at least start thinking about supported platforms, @cjihrig pointed out that libuv has a list now @ libuv/libuv@be0e24c and this may be something the Build WG takes as a starting-point. For the purposes of this meeting I suggest we remove it and just keep the meeting short.

[jbergstroem]

The build group will have something ready for its next meeting, September 27.

[trevnorris]

@Trott After completing the implementation and doing some testing/benchmarking found that it fell short of performance goals. So I partially implemented a change to the embedder API, and now that it's looking sound I'm updating the EP at this moment. The public API as currently defined in the EP will remain the same.

[trevnorris]

The EP is updated with the new embedder API.

[jasnell]

Given the light schedule today, I'm going to go ahead and skip this one. I've already offered my feedback on the various issues on the agenda in the relevant github threads.