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

[mhdawson]

Time

UTC Wed 18-Oct-2017 17:00 (05:00 PM):

Timezone	Date/Time
US / Pacific	Wed 18-Oct-2017 10:00 (10:00 AM)
US / Mountain	Wed 18-Oct-2017 11:00 (11:00 AM)
US / Central	Wed 18-Oct-2017 12:00 (12:00 PM)
US / Eastern	Wed 18-Oct-2017 13:00 (01:00 PM)
Amsterdam	Wed 18-Oct-2017 19:00 (07:00 PM)
Moscow	Wed 18-Oct-2017 20:00 (08:00 PM)
Chennai	Wed 18-Oct-2017 22:30 (10:30 PM)
Hangzhou	Thu 19-Oct-2017 01:00 (01:00 AM)
Tokyo	Thu 19-Oct-2017 02:00 (02:00 AM)
Sydney	Thu 19-Oct-2017 04:00 (04:00 AM)

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-18&iso=20171018T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Oct+18%2C+2017+in+local+time

Links

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

Agenda

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

Workgroup Update

Benchmarking WG Update

nodejs/build

• tmp dir needed on ubuntu 1604 and fedora23 #873

nodejs/node

• Support both OpenSSL 1.1.0 and 1.0.2 #16130
• 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
• http2: expose http2 by default, add NODE_NO_HTTP2 #15684

nodejs/TSC

• Proposal to form a Governance Working Group #383
• doc: adjust voting rules #378
• Who should be in @nodejs/security? Who should have access to the private repo? #358

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

[jasnell]

I would like to invite @dshaw as a regular observer, his input is particularly valuable in governance discussions such as #383, #378 and #358.

[mhdawson]

As an FYI these are the tsc-review items for this week

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

• 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

[fhinkel]

Are we doing these weekly now instead of bi-weekly?

[mcollina]

@fhinkel yes, we decided this some times ago. There seems to be more activity as we are closer to the 9 release.

[MylesBorins]

I'd like to invite @sarahnovotny as an observer, they expressed interest at node Interactive and we appeared to have consensus that it was a good idea

[mcollina]

👍 for inviting @sarahnovotny

[mhdawson]

I'm + 1 for inviting @dshaw and @sarahnovotny as observers if they are intersted.

[dshaw]

Thank you. I am available during the scheduled time and will attend if invited.

[jasnell]

@dshaw ... unless there are explicit objections between now and then, please consider yourself invited.

[Trott]

#378 can be removed from the agenda, I think.

[Trott]

#378 can be removed from the agenda, I think.

Although only if @mhdawson (who put it on the agenda) concurs. Otherwise, it stays on. Those are the rules. :-D

[Trott]

a regular observer

Not objecting but getting this on the radar: I've been considering suggesting that we not have "regular observers" anymore but that observers get invited when it is relevant. I think having regular observers creates a club and implies some elitism TBH, whereas having to specifically think about who to invite each week is probably healthy. It is especially healthy if it causes us to cast our net a little wider on who we invite.

Should we invite bmeck any time we are discussing anything that touches on ES Modules? Absolutely. Should they get invited to every single meeting? I'm not sure that makes sense. (And I suspect Bradley would agree with that assessment.)

[Trott]

Are we doing these weekly now instead of bi-weekly?

@fhinkel Yeah, that was the agreement a month or two ago because we had full agendas for the meetings. The hope was that we'd get back to doing things more asynchronously and being able to cancel most meetings again. (And then we could consider moving to bi-weekly. But we're not there yet, IMO.)

[Trott]

Looking at the list of five regularly invited observers, none of them attend regularly. Nor should they, IMO. I'm tempted to add an agenda item saying that we should get rid of regularly invited observers. I'm happy to submit the PR to the tooling that makes the meetings.

[williamkapke]

I have always attended regularly. Only recently, with the adoption of the former CTC schedule, has it started to conflict for me.

... but if I've overstayed my welcome- just let me know.