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

[mhdawson]

Time

UTC Wed 29-Aug-2018 16:00 (04:00 PM):

Timezone	Date/Time
US / Pacific	Wed 29-Aug-2018 09:00 (09:00 AM)
US / Mountain	Wed 29-Aug-2018 10:00 (10:00 AM)
US / Central	Wed 29-Aug-2018 11:00 (11:00 AM)
US / Eastern	Wed 29-Aug-2018 12:00 (12:00 PM)
London	Wed 29-Aug-2018 17:00 (05:00 PM)
Amsterdam	Wed 29-Aug-2018 18:00 (06:00 PM)
Moscow	Wed 29-Aug-2018 19:00 (07:00 PM)
Chennai	Wed 29-Aug-2018 21:30 (09:30 PM)
Hangzhou	Thu 30-Aug-2018 00:00 (12:00 AM)
Tokyo	Thu 30-Aug-2018 01:00 (01:00 AM)
Sydney	Thu 30-Aug-2018 02:00 (02:00 AM)

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1sGHdNAQnFPwny4YTDr0kZYJDer2-L0NXGKJXIxSVhLM/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
  Edit fhinkel: Not on the agenda anymore. Please have a look and decide between the approach in #22218 and #21857
• util: expose promise events #21857
• Password Hashing API #21766
• 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

nodejs/admin

• JS Interactive & Node Community Corner - Questions? #211

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

[TimothyGu]

@jasnell … so I see nodejs/node#22352 on the agenda. Is there something specific you would like to talk about at the meeting? (If we want to have the API at all, the technical approach used by this PR, or something else…)

Would love to get some clarification.

[mcollina]

@TimothyGu my objection is firstly around process. That is not something that I'm comfortable in reviewing and landing atm as a single PR. The amount of code and its implication are staggering.

We delayed talking about it to wait for @Fishrock123 feedback.

[Fishrock123]

I've added a large chunk of feedback to the WhatWG streams PR (link) and will be present at this week's meeting.

[fhinkel]

Can we remove nodejs/node#22352 from the agenda? There are multiple TSC members requesting similar changes. There is no TSC member that wants to land it as is.

[fhinkel]

@MylesBorins , why did you add nodejs/node#22302 to the agenda? I think feature detection in core is better discussed in the issue than in the meeting.

[fhinkel]

@BridgeAR Is it OK if we remove nodejs/node#22218 from the agenda? There was constructive discussion until 4 days ago. I don't think it's the right time for the TSC to make decisions, or rather, the issue is open to all TSC member to leave their opinion anyways.

[fhinkel]

@seishun Does nodejs/node#21351 need to be on the agenda? Looks like there's active discussion and an open comment in the issue.

[fhinkel]

TSC peeps, if you have time, you should weigh in on these issues. They all make fairly fundamental changes to Node core.

• 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
• buffer: runtime-deprecate Buffer constructor everywhere by default #21351

In my experience, technical questions are best solved by clearly written comments and code reviews, not in conference meetings.

All five issues are on the tsc-agenda. I think it's only fair to the contributors to reviews them sooner than later so they can land or be changed appropriately. Waiting another 4 weeks is not going to make it easier for us to decide if we want or don't want a feature.

[mcollina]

Unfortunately I won't be able to attend this meeting for personal reasons.

I've reviewed all the PRs, and I prefer nodejs/node#22218 over to nodejs/node#21857 even though I LGTM both.

[targos]

Pinging invited observers: @apapirovski, @gabrielschulhof

[BridgeAR]

@fhinkel I am totally fine to remove it from the agenda if more TSC members weight in on the PRs themself as long as we find an agreement due to enough LGs on either one :)

I would like to get this sorted out soon.

[fhinkel]

@BridgeAR Thanks!

[ChALkeR]

Sorry, won't be able to participate today due to personal reasons.

nodejs/node#22302 — my opinion has not changed since nodejs/node#22302 (comment). I read the comments. I think that we should do mkdirp as the most simple solution. I might change my opinion on more input though (as always), and am ready to discuss that, but just not today, sorry.
nodejs/node#21766 — no updates 😞, but I hope to have by next week.
nodejs/node#21351 — filed nodejs/node#22584, would appreciate comments there.

[Trott]

Moderation Team Report: No moderation actions to report this week.

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