Node.js Foundation Core Technical Committee (CTC) Meeting 2016-02-03

[rvagg]

Time

UTC Wed 03-Feb-2016 20:00:

• San Francisco: Wed 03-Feb-2016 12:00
• New York: Wed 03-Feb-2016 15:00
• Amsterdam: Wed 03-Feb-2016 21:00
• Moscow: Wed 03-Feb-2016 23:00
• Sydney: Thu 04-Feb-2016 07:00
• Tokyo: Thu 04-Feb-2016 05:00

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1BHZcpGfLL8MSGwGvEHAF9ojBEVocWmNV3-y6kB4Xp4Y
• Previous Minutes Google Doc: https://docs.google.com/document/d/145ND-9pGdAwZ1eoOMypX1_wtx5FCVoanWtLl8zzyxH8

Agenda

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

nodejs/node

• Enable Node.js to run with Microsoft's ChakraCore engine #4765
• CTC Membership Nominations #4750
• buffer: add Buffer.from(), Buffer.alloc() and Buffer.allocUnsafe(), soft-deprecate Buffer(num) #4682
• Buffer(number) is unsafe #4660
• Seek legal advice on LICENSE and copyright blocks in code #3979

Invited

• @bnoordhuis (CTC)
• @ChALkeR (observer)
• @chrisdickinson (CTC)
• @cjihrig (CTC)
• @domenic (observer)
• @evanlucas (observer)
• @Fishrock123 (CTC)
• @indutny (CTC)
• @jasnell (CTC)
• @mhdawson (observer)
• @misterdjules (CTC)
• @mikeal (observer)
• @mscdex (CTC)
• @ofrobots (observer)
• @orangemocha (CTC)
• @piscisaureus (CTC)
• @rvagg (CTC)
• @shigeki (CTC)
• @srl295 (observer)
• @trevnorris (CTC)
• @Trott (observer)

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.

[rvagg]

There's nothing new on this agenda (yet) so we might get away with a quick meeting.

@nodejs/ctc and others in the security team: PLEASE review the security issues being discussed in the security repo, the two at the top of the list @ https://github.com/nodejs/security/issues are in play and it's essential that we pin it down in this meeting (during private section) so we can get the security releases out without a last-minute scramble or post-release regrets! There's some breaking change discussion we need to have. I'm going to add our new CTC candidates to the security team so they can look too and get up to speed and perhaps form opinions (note that we have other non-CTC members on that group so this is not a special case or a presumption that they will automatically be getting CTC membership). I'll post a comment in that top issue straight after posting this comment that attempts to summarise the status and what we need to decide on, @jasnell can follow up if I need correcting on the details.

[ofrobots]

Regrettably, I will have to miss this and the subsequent two CTC meetings as I am on vacation, and with spotty wifi, until Feb 16th.

[orangemocha]

Related to #4765, I also tagged nodejs/roadmap#54 as it seems that that's where we need to come to a resolution first.

[piscisaureus]

I'll also pass this week.

[rvagg]

Audio Recording: https://soundcloud.com/node-foundation/ctc-meeting-2016-02-03

Minutes being merged @ #5272