Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-10-11

[mhdawson]

Time

UTC Wed 11-Oct-2017 12:00 (12:00 PM):

Timezone	Date/Time
US / Pacific	Wed 11-Oct-2017 05:00 (05:00 AM)
US / Mountain	Wed 11-Oct-2017 06:00 (06:00 AM)
US / Central	Wed 11-Oct-2017 07:00 (07:00 AM)
US / Eastern	Wed 11-Oct-2017 08:00 (08:00 AM)
Amsterdam	Wed 11-Oct-2017 14:00 (02:00 PM)
Moscow	Wed 11-Oct-2017 15:00 (03:00 PM)
Chennai	Wed 11-Oct-2017 17:30 (05:30 PM)
Hangzhou	Wed 11-Oct-2017 20:00 (08:00 PM)
Tokyo	Wed 11-Oct-2017 21:00 (09:00 PM)
Sydney	Wed 11-Oct-2017 23:00 (11:00 PM)

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1PkoiLPj1b_ePtCL6IWDSwI-eh1Vzp7sfhu5deoiWM-A/edit?usp=sharing
• Previous minutes: https://docs.google.com/document/d/1DRhvfRAbp1EILu3h2iwSi8Efj7ghAE0fdu8X3CvvSGQ_

Agenda

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

Workgroup Update

Release Work Group

nodejs/build

• tmp dir needed on ubuntu 1604 and fedora23 #873

nodejs/node

• async_hooks: skip sanity checks when disabled #15454
• buffer: runtime-deprecate Buffer ctor by default #15346
• http: send 400 bad request on parse error #15324
• stream: move prefixed files into internal/streams. #11957

nodejs/TSC

• Who should be in @nodejs/security? Who should have access to the private repo? #358
• Vote on the approach for Cleanup _writableState and _readableState access across codebase node#445 #355

nodejs/admin

• doc: doc expectations on TSC and CommComm members #12

Invited

• Anna Henningsen @addaleax (TSC)
• Ben Noordhuis @bnoordhuis (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Evan Lucas @evanlucas (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• Fedor Indutny @indutny (TSC)
• James M Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Brian White @mscdex (TSC)
• Myles Borins @MylesBorins (TSC)
• Ali Ijaz Sheikh @ofrobots (TSC)
• Rod Vagg @rvagg (TSC)
• Shigeki Ohtsu @shigeki (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Trevor Norris @trevnorris (TSC)
• Rich Trott @Trott (TSC)
• Josh Gavant @joshgav (TSC)

Observers

• Bradley Meck @bmeck (GoDaddy/TC39)
• Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
• Kaitlyn Barnard @kbarnard10 (Node.js Foundation Newsletter Curator)
• Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
• William Kapke @williamkapke (Node.js Community Board representative)

Notes

The agenda comes from issues labelled with tsc-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 TSC that's not worth putting on as a separate agenda item, this is a good place f

[mhdawson]

@mcollina has volunteering to do the streaming in #376

[mhdawson]

Issues marked tsc-review for awareness:

nodejs/build

• Dropping 32-bit builds #885

nodejs/node

• buffer: runtime-deprecate Buffer(num) by default #15608
• console,doc: add inspector console object #15579
• repl: support top-level await #15566
• http: send 400 bad request on parse error #15324
• Regression: Resolution algorithm collision #14990
• build: update minimum kernel version to 3.10.0 #14795
• module: remove unnecessary nonInternalExists check #14664
• Buffer.isEncoding regards an empty string as a valid encoding #9654

nodejs/TSC

• Vote on the approach for Cleanup _writableState and _readableState access across codebase node#445 #355
• Candidate "areas" for TSC and Community Committee #278
• Approval to move node-heapdump into foundation #257

nodejs/node-eps

• Invert dependency between core and readable-stream #49

[targos]

I won’t be able to attend this meeting and the next (visiting Canada).

[MylesBorins]

I'd like to discuss the 8.7.0 release, V8 6.2, and the escape analysis problem in general

[Trott]

The agenda is pretty packed and has a lot of items that might require lengthy discussion. We may want to prioritize items, taking into consideration who attends.

[addaleax]

I won’t be able to make it, sorry. (Edit: Could somebody give me the google doc link with the time slots again? I might need to make a few adjustments starting now…)

[mscdex]

I won't be there either.

[cjihrig]

I don't have reliable internet right now, so I won't be able to make it.

[Trott]

#355 has been resolved. @mcollina added it to the agenda so I believe only he can remove it (per our governance rules). But even if it stays on the agenda, it sould be pretty quick.

[evanlucas]

I won’t be able to make it tomorrow.

[ChALkeR]

I am likely to miss this today or be late, due to a time conflict.
I hope to make it in time, though!

[mhdawson]

PR for minutes: #379

[jasnell]

My apologies for missing today. It was a bit too early in the morning for me.

[ofrobots]

Apologies for missing the meeting today as well. Slightly too early in the day for me.

[thefourtheye]

Sorry. I was not able to attend as I was working on a production issue.