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

[Trott]

Time

UTC Wed 10-Aug-2016 20:00:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1L65L7qhX5MrGeFwrub4-Z8klrwxJym-Q8CIEZsedohE
• Previous Minutes Google Doc: https://docs.google.com/document/d/1ufR5dNuN3JLmFPvCvLYGRa98_-eqy5yY3zJuTnT60K8

Agenda

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

nodejs/node

• v4.5.0 proposal #7688
• buffer: hard-deprecate Buffer constructor #7152
• Revert "fs: add a temporary fix for re-evaluation support" #6413
• errors: add internal/errors module #6573
• Introduce staging branch for stable release streams #6306

nodejs/node-eps

• proposal: WHATWG URL standard implementation #28
• discussion: modules interop overhaul (https://gist.github.com/bmeck/52ee45e7c34d1eac44ce8c5fe436d753)

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)
• Alexis Campailla @orangemocha (observer)
• Bert Belder @piscisaureus (observer/IBM)
• Rod Vagg @rvagg (CTC)
• Seth Thompson @s3ththompson (observer/Google)
• Shigeki Ohtsu @shigeki (CTC)
• Steven R Loomis @srl295 (observer/IBM/ICU)
• Myles Borins @thealphanerd (observer/IBM)
• 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.

[indutny]

May not be able to join today. Just in case:

• v4.5.0 - no opinion, why not?
• dropping support for VS 2013 - 👍
• buffer: runtime-deprecate Buffer constructor #7152 - -0
• dgram,test: add addMembership/dropMembership tests #6753 - some performance nits, otherwise 👍

[ChALkeR]

@indutny

#6753

You meant #6573, correct?

[Trott]

May not be able to join today. Just in case:

@indutny: Note the meeting is tomorrow (not today). ...in case that makes a difference and in case anyone else might think it's today...

I'm trying to open these issues with more than 24 hours of lead time before the meeting. (I can stop doing that if it isn't helpful.)

[jasnell]

It's very helpful, thank you.

[ChALkeR]

@Trott Could we add #6413 to the agenda? I think it's ready to be merged.

#6573, depends on that one, btw.

[Trott]

@ChALkeR Added! By the way, any CTC member is permitted to add items to the agenda, so if you want, you can just add it above, add it to the Google doc, and leave a comment letting folks now. Hmmm, now that I've typed that out, I guess asking me (or Rod or whoever) to do it is probably easier...

[ChALkeR]

@Trott Thanks! 😉

[Trott]

Oh, and I forgot to mention before: Standup section is ready to be filled out if you don't want to be doing it during the meeting!

[Trott]

Also: Reminder that tomorrow is supposed to be The Big Conversation about nodejs/node-eps#28 so please be prepared to discuss that if you feel that you have a stake in it. As far as I've been able to determine, the only Big Sticking Point is some opposition to a URL global. If you have other objections, please be prepared to articulate them (or better yet, make sure they are articulated in that issue).

[jasnell]

Given that it would be going in as experimental, I don't think it not being
as global is really all that much of an issue. If we land it, we can always
make it a global later if necessary.

On Tuesday, August 9, 2016, Rich Trott [email protected] wrote:

Also: Reminder that tomorrow is supposed to be The Big Conversation about
nodejs/node-eps#28 nodejs/node-eps#28 so please
be prepared to discuss that if you feel that you have a stake in it. As far
as I've been able to determine, the only Big Sticking Point is some
opposition to a URL global. If you have other objections, please be
prepared to articulate them (or better yet, make sure they are articulated
in that issue).

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

[shigeki]

Regrets and very sorry for my long absence. I will be back in a few week.

[Trott]

@bmeck Given your comments in IRC, should we add a modules item to the agenda? Or is it more of a 30-second update you want to say during the Standup and then maybe have to conversation move to GitHub?

[MylesBorins]

It is likely a bit too late to add this to the agenda but if we have time I would like to discuss

#6306
Introduce staging branch for stable release streams

I know that we have had some back and forth on this but I do feel quite strongly that we should have a single release process for all streams that involves regular backporting to a staging branch.

If there is not time this week I would like to have it added to next week's agenda

[misterdjules]

My apologies: I won't be able to attend the meeting today.

[Trott]

We had the meeting, so I'm going to close the issue. At least, I think that's the protocol...

[joshgav]

@Trott - I sometimes close it via the notes PR if we want that to be the protocol.