Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-04-24

[mhdawson]

Time

UTC Wed 24-Apr-2019 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Wed 24-Apr-2019 14:00 (02:00 PM)
US / Mountain	Wed 24-Apr-2019 15:00 (03:00 PM)
US / Central	Wed 24-Apr-2019 16:00 (04:00 PM)
US / Eastern	Wed 24-Apr-2019 17:00 (05:00 PM)
London	Wed 24-Apr-2019 22:00 (10:00 PM)
Amsterdam	Wed 24-Apr-2019 23:00 (11:00 PM)
Moscow	Thu 25-Apr-2019 00:00 (12:00 AM)
Chennai	Thu 25-Apr-2019 02:30 (02:30 AM)
Hangzhou	Thu 25-Apr-2019 05:00 (05:00 AM)
Tokyo	Thu 25-Apr-2019 06:00 (06:00 AM)
Sydney	Thu 25-Apr-2019 07:00 (07:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2019-04-24&iso=20190424T21
• or http://www.wolframalpha.com/input/?i=09PM+UTC%2C+Apr+24%2C+2019+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1AVUmlbwx33Wndbj5vXnrFsZbs6EVSgeyqS_HmeT7bjI/edit

Agenda

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

nodejs/node-gyp

• v3.8.1 proposal #1718

nodejs/node

• Piping w/ spawn is broken in Node 11 #27097

nodejs/TSC

• CFP review process for Node+JS Interactive - Sarah from foundation.
• Nominating @jasnell to rejoin TSC #694
• TSC Elections Chair and CPC representative. #689
• Tracking issue for updating TSC on Board Meetings #476
• Strategic Initiatives - Tracking Issue #423

Invited

• Anna Henningsen @addaleax (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• Gabriel Schulhof @gabrielschulhof (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Rod Vagg @rvagg (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Rich Trott @Trott (TSC)

Observers/Guests

• Sam Roberts @sam-github (observer)

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.

---

Invitees

Please use the following emoji reactions in this post to indicate your
availability.

• 👍 - Attending
• 👎 - Not attending
• 😕 - Not sure yet

[richardlau]

I added the tsc-agenda label to nodejs/node-gyp#1718 so I'll attempt to summarize:
npm audit is flagging up a security issue for version of tar < 4.4.2. The latest version of node-gyp available in the npm registry is 3.8.0, published 8 months ago, which uses tar v2 (and is therefore marked vulnerable). We did actually update the master branch of node-gyp to use tar v3 in June 2017 but that was deemed a breaking (i.e. semver-major) change. As yet we have not released node-gyp v4, some twenty months on.

I've added nodejs/node-gyp#1718 to the agenda because it appears to be stuck and, as far as I know, node-gyp doesn't fall under the umbrella of any of the working groups that the TSC has delegated authority to (while it is listed as an adjacent project in the TSC readme). The solution may be as simple as publishing a new version of node-gyp from its master branch, although the number of people who can publish node-gyp to npm (I'm not one of them) is small and (from issue/pull request history) non-active.

Unfortunately I am technically on vacation until the second week of May so will probably be unable to attend the TSC meeting.

[ChALkeR]

@richardlau I left a comment about node-gyp.

[SarahKConway]

@mhdawson would the group be open to me joining tomorrow to talk about the CFP review process for Node+JS Interactive? We're looking for volunteers for this year's CFP review committee.

[mhdawson]

@SarahKConway sounds good to me, I'll add to the agenda.

[mhdawson]

I removed nodejs/security-wg#516 as we discussed it last week and just missed removing the agenda tab.

[Trott]

Since I'm a "no" and @rvagg is a "maybe" on this meeting, I'll put the Build strategic initiative stuff here now: Last week, I said I'd put together a doc describing the problem and possible solutions. I finally started that doc just now. So, uh, it will be a little late. But it's in progress now.

[SarahKConway]

I am trying to join the meeting and I think that a password is required. Can someone please email me the password at [email protected]?

[Trott]

PR for minutes: #697