Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-08-22

[mhdawson]

Time

UTC Wed 22-Aug-2018 12:00 (12:00 PM):

Timezone	Date/Time
US / Pacific	Wed 22-Aug-2018 05:00 (05:00 AM)
US / Mountain	Wed 22-Aug-2018 06:00 (06:00 AM)
US / Central	Wed 22-Aug-2018 07:00 (07:00 AM)
US / Eastern	Wed 22-Aug-2018 08:00 (08:00 AM)
London	Wed 22-Aug-2018 13:00 (01:00 PM)
Amsterdam	Wed 22-Aug-2018 14:00 (02:00 PM)
Moscow	Wed 22-Aug-2018 15:00 (03:00 PM)
Chennai	Wed 22-Aug-2018 17:30 (05:30 PM)
Hangzhou	Wed 22-Aug-2018 20:00 (08:00 PM)
Tokyo	Wed 22-Aug-2018 21:00 (09:00 PM)
Sydney	Wed 22-Aug-2018 22:00 (10:00 PM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2018-08-22&iso=20180822T12
• or http://www.wolframalpha.com/input/?i=12PM+UTC%2C+Aug+22%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/17NjZTOM6-xZF53psjsylXDrPkXfVjFLdhAL7duxMGCA/edit

Agenda

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

nodejs/node

• stream-whatwg: add whatwg streams #22352
• [WIP] fs: feature detection for recursive mkdir[Sync] #22302
• process: add resolveSwallowed event #22218
• util: expose promise events #21857
• Password Hashing API #21766
• tty: make _read throw ERR_TTY_WRITABLE_NOT_READABLE #21654
• buffer: runtime-deprecate Buffer constructor everywhere by default #21351

nodejs/TSC

• update charter #569
• Tracking issue for updating TSC on Board Meetings #476
• Strategic Initiatives - Tracking Issue #423

Invited

• Anna Henningsen @addaleax (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gibson Fahnestock @gibfahn (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• James M Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Ali Ijaz Sheikh @ofrobots (TSC)
• Rod Vagg @rvagg (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Timothy Gu @TimothyGu (TSC)
• Rich Trott @Trott (TSC)

Observers/Guests

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

Zoom link: https://zoom.us/j/611357642
Regular password

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 for that

[Trott]

• Proposal: add all new core modules under a scope? (too late for http2) #389

After the TSC meeting three weeks ago, @mhdawson commented:

In the last TSC meeting we discussed again, there were no strong objections.

Unfortunately, there don't appear to be minutes from that meeting and I don't see a video at https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ/videos.

The minutes provide a few more details, but leave me unsure about:

Can that statement be interpreted as the following?: "The TSC is tentatively in favor of proceeding with namespacing for future core modules. Let's move to the implementation and code review stage. There is a possibility that we will reverse the decision and the implementation will not land, but for now at least, let's proceed and see what happens."

FWIW, here's how I see TSC sentiment in that issue. Please comment if I've misrepresented you or your view is not represented at all.

Yes, let's namespace! 6: @Trott @ofrobots @MylesBorins @targos @joyeecheung @cjihrig

Neutral-ish. 2: @jasnell @rvagg

Skeptical or solid "no". 3: @Fishrock123 @mcollina @addaleax

View not represented. 7 @fhinkel @mhdawson @thefourtheye @ChALkeR @danbev @gibfahn @TimothyGu

/cc @ljharb

[fhinkel]

@Trott, the meeting 3 weeks ago was cancelled because of Node Summit. The "last meeting" @mhdawson is referring to is this one: 2018-07-18

[Trott]

Thanks, @fhinkel! I thought he was referring to https://github.com/nodejs/TSC/blob/master/meetings/2018-08-01.md. As it turns out, both sets of minutes have small pieces of the puzzle documented in them. Completists will need to look at both. :-D

[mhdawson]

My understanding on Proposal: add all new core modules under a scope? (too late for http2) #389

• Several people are not a fan of namespacing but not concerned enough to block
• As there are no objections, it can proceed and details will be worked out through the PR process.

And we should have removed from the agenda. @Trott since you added it to the agenda maybe you can remove it you agree.

[Trott]

@Trott since you added it to the agenda maybe you can remove it you agree.

Will do!

[Fishrock123]

I would like nodejs/node#22352 (stream-whatwg: add whatwg streams) to be delayed until next week. I have a lot of investment in this subject, although I haven't gotten to commenting on the thread yet.

I also forgot that this was the early meeting and won't be able to make it tomorrow.

[Trott]

Moderation Team update:

• Off-topic comments hidden and conversation locked for an old commit. Moderation issue 227.
• An issue was locked and comments hidden. A Moderation Team member reached out to participants, unlocked the issue, revealed the comments, and left a comment to facilitate productive conversation. Moderation issue 228.

@nodejs/moderation @nodejs/community-committee @nodejs/tsc

[mhdawson]

PR for minutes: #588