Node.js Foundation Core Technical Committee (CTC) Meeting 2016-08-31

[Trott]

Time

UTC Wed 31-Aug-2016 20:00:

Timezone	Date/Time
US / Pacific	Wed 31-Aug-2016 13:00
US / Mountain	Wed 31-Aug-2016 14:00
US / Central	Wed 31-Aug-2016 15:00
US / Eastern	Wed 31-Aug-2016 16:00
Amsterdam	Wed 31-Aug-2016 22:00
Berlin	Wed 31-Aug-2016 22:00
Moscow	Wed 31-Aug-2016 23:00
Tokyo	Thu 01-Sep-2016 05:00
Sydney	Thu 01-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-08-31&iso=20160831T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Aug+31%2C+2016+in+local+time

Links

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

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
• child_process, win: fix shell spawn with AutoRun #8063
• fs: undeprecate existsSync; use access instead of stat for performance #7455
• doc: add Google Analytics tracking. #6601
• Introduce staging branch for stable release streams #6306
• Move ecosystem detection tool to nodejs org #7935

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)
• Bert Belder @piscisaureus (observer)
• 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]

For most participants, this meeting will take place on Wednesday afternoon/night or Thursday morning. The meeting will take place 41.5 hours from the time of this writing.

[Trott]

Standup portion of the doc is ready to be filled in.

[rvagg]

@Trott care to chair this one? I'm still quite out of sync and mostly have my head in Foundation business and a bunch of Build WG stuff.

[hackygolucky]

Away from email/slack/phone during this meeting. No updates from last week.

On Wed, Aug 31, 2016, 8:09 AM Rod Vagg notifications@github.com wrote:

@Trott https://github.com/Trott care to chair this one? I'm still quite
out of sync and mostly have my head in Foundation business and a bunch of
Build WG stuff.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#8330 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB46oEZIdR3VmgG48zZgVLdtJWgPKMqZks5qlW7pgaJpZM4JwFVJ
.

[ChALkeR]

Could we add #7935 for a brief discussion if there would be some time left?

[MylesBorins]

I unfortunately will not be able to make the meeting this time. I still believe that we should have a single release process across all lines, which includes having a staging branch for current. Consistency makes it easier for us to on board individuals, and makes it easier for contribution between the various release lines.

[Fishrock123]

@thealphanerd Last week I was told consistency was not the issue...

[MylesBorins]

@Fishrock123 it is one of a few issues I've brought up in the past. Others include:

• Handling conflicts in advance
• having a place to land things intermediately that does not pollute the release branch

Having done both current + LTS releases I have personally found that it adds work prior to the release, but significantly simplifies the process on release day.

TBQH I think that the discussion has gone back and forth quite a bit. If the individuals who are primarily doing the current releases are reluctant then I'll let it be.

[ofrobots]

It is more than just the releasers that should be considered. As someone who ends up doing, or help others do, quite a few V8 backports, the lack of uniformity of process on how to backport things to all the release branches is a big problem. Consistency is an issue for me.

[Trott]

@Trott care to chair this one? I'm still quite out of sync and mostly have my head in Foundation business and a bunch of Build WG stuff.

I'm traveling and will be on cafe WiFi. Should be OK, but we should have a Plan B and Plan C if it doesn't work out for me.

Plan B = @jasnell?

Plan C = whoever wants to do it can volunteer?

Plan D = @rvagg does it whether he wants to or not?

[misterdjules]

I won't be able to make it today.

[jasnell]

Not sure how well I would work as a Plan B today, unfortunately. The kids get out of school at 1pm pacific and I have to drop them off at their Robotics club meeting right after so I'm going to be mobile and away from the laptop for most of the call.... I'll be on the call, just won't have convenient access to the notes or agenda and will have to mute frequently

[Trott]

OK, I think I'm good to run this one. Can someone email (or otherwise private message) me the dial-in info just in case WiFi availability torpedoes my audio stream? EDIT: Thanks to @bmeck, I now have the info.

[chrisdickinson]

Apologies, I won't be able to attend today.