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

[mhdawson]

Time

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

Timezone	Date/Time
US / Pacific	Wed 08-Aug-2018 09:00 (09:00 AM)
US / Mountain	Wed 08-Aug-2018 10:00 (10:00 AM)
US / Central	Wed 08-Aug-2018 11:00 (11:00 AM)
US / Eastern	Wed 08-Aug-2018 12:00 (12:00 PM)
London	Wed 08-Aug-2018 17:00 (05:00 PM)
Amsterdam	Wed 08-Aug-2018 18:00 (06:00 PM)
Moscow	Wed 08-Aug-2018 19:00 (07:00 PM)
Chennai	Wed 08-Aug-2018 21:30 (09:30 PM)
Hangzhou	Thu 09-Aug-2018 00:00 (12:00 AM)
Tokyo	Thu 09-Aug-2018 01:00 (01:00 AM)
Sydney	Thu 09-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-08&iso=20180808T16
• or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Aug+08%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1dWg53W1QJS2behLznKdkRQ0nuGXvXdq1e-MBNyUcsuM/edit

Agenda

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

nodejs/build

• Request for elevated permissions #1337

nodejs/node

• Collaborator nomination - gdams #21934
• fs: implement recursive (mkdirp) functionality #21875
• 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

• Tracking issue for updating TSC on Board Meetings #476
• Strategic Initiatives - Tracking Issue #423
• Proposal: add all new core modules under a scope? (too late for http2) #389

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

• Anatoli Papirovski @apapirovski
• Gabriel Schulhof @gabrielschulhof

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]

This time is usually excellent for me, but alas, not this week.

/pinging @apapirovski and @gabrielschulhof for attendance as observers.

[ChALkeR]

Sorry, I am most likely not be able to participate today, for personal reasons. This time is usually good, but this week is unusual.

@mhdawson, I added nodejs/node#21766 to the agenda, last time we came to a resolution that I will draft a PR, but I didn't finish that yet. I do not have updates atm. My suggestion would be to take it off the agenda today and return to it next week.

Re: nodejs/node#21351 — I have a proposal mentioned in that issue, please also keep that one in mind while discussing this. I would like to see some objections against doing at least that (i.e. for favoring doing nothing over emitting warnings for first ticks) on GitHub first before it would be rejected by a TSC vote. It also needs some tests to check just how many additional modules would be affected. Perhaps CITGM?

Collaborator nomination — yay! 🎉

[Trott]

Moderation Team report for the week: One comment was hidden as off-topic and possible trolling. Moderation issue 224.

And that's it!

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

[apapirovski]

Commuting so will listen in but won't truly join till 15 after or so.

[mhdawson]

PR for minutes: #582