Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-11-06

[mhdawson]

Time

UTC Wed 06-Nov-2019 15:00 (03:00 PM):

Timezone	Date/Time
US / Pacific	Wed 06-Nov-2019 07:00 (07:00 AM)
US / Mountain	Wed 06-Nov-2019 08:00 (08:00 AM)
US / Central	Wed 06-Nov-2019 09:00 (09:00 AM)
US / Eastern	Wed 06-Nov-2019 10:00 (10:00 AM)
London	Wed 06-Nov-2019 15:00 (03:00 PM)
Amsterdam	Wed 06-Nov-2019 16:00 (04:00 PM)
Moscow	Wed 06-Nov-2019 18:00 (06:00 PM)
Chennai	Wed 06-Nov-2019 20:30 (08:30 PM)
Hangzhou	Wed 06-Nov-2019 23:00 (11:00 PM)
Tokyo	Thu 07-Nov-2019 00:00 (12:00 AM)
Sydney	Thu 07-Nov-2019 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+2019-11-06&iso=20191106T15
• or http://www.wolframalpha.com/input/?i=03PM+UTC%2C+Nov+06%2C+2019+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/13kmh_Y7DJpmXHfLg8iErAFswiwFOAjYCNGYaW3erJb4/edit

Agenda

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

nodejs/node

• macOS Installer Requires Notarization To Be Run Under Catalina and Beyond #29216

nodejs/admin

• Should we host a code and learn in Montreal #432
• Collaborator Summit - Montreal 2019 #416

Invited

• Anna Henningsen @addaleax (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Beth Griggs @BethGriggs (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)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Sam Roberts @sam-github (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Tobias Nießen @tniessen (TSC)
• Rich Trott @Trott (TSC)

Observers/Guests

• Christian Clauss @cclauss (guest participant)

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

[Trott]

For macOS Installer Requires Notarization To Be Run Under Catalina and Beyond, is there anything for TSC to decide or do here? Or is it a Releasers process/issue? @sam-github

For Should we host a code and learn in Montreal, I think the answer has been determined (in email) to be "Not this time" and that we will reclaim the time for the Collaborators Summit. If that's wrong, someone correct me. If that's right, should we remove it from the agenda? @mcollina

[richardlau]

I stuck a tsc-review label on nodejs/build#1913 at the end of last week as it appears to have stalled with the last comments being to take it to the TSC.

For macOS Installer Requires Notarization To Be Run Under Catalina and Beyond, is there anything for TSC to decide or do here? Or is it a Releasers process/issue? @sam-github

From the most recent Build WG meeting it was suggested the TSC be made aware that we don't have anyone with time to pick up this work and unanswered questions as to whether we would be okay with the 8.x and 10.x LTS releases not running on the latest version of macOS since it looks like we would have to move to a later release machine and build chain which is something we have avoided in the past within the lifetime of a release.

[Trott]

If they're available, I'd be in favor of inviting @richardlau as a guest to make sure we have good context for macOS Installer Requires Notarization To Be Run Under Catalina and Beyond. I suspect @sam-github and others can provide context, but better to have more people than we need to provide context than no one....

[richardlau]

I'm not actually a macOS user so all of my information on notarization has come secondhand from @AshCripps (who guested at the last Build WG meeting) and @sam-github.

[rvagg]

An FYI report from another part of Build: after experiencing download problems from nodejs.org in the last 2 weeks due to exceeding our normal bandwidth and apparently hitting some underlying hardware limits, due to a combination of normal continued growth and growth in binary size, we've hastened our long-overdue move to full CDNification of downloads.

• Original reports of download problems and attempts to mitigate: SLOW OR FAILED (500 ERROR) NODE.JS DOWNLOADS build#1993
• Current discussion of the migration of our download logs and metrics and some details of Cloudflare configuration: ansible: metrics server (WIP) & removal of Cloudflare cache bypass build#2025

Going well (times are my tz):

And we're continuing to ensure we have the caching right and making sure we have fully offline capable binaries (i.e. if our two backend servers die) and still retain our ability to generate metrics from downloads.

Kudos is due to our donors, DigitalOcean for being so responsive on the hardware problems when we finally reached out to them, and to Cloudflare who we are working with to level up our CDN strategy.

[sam-github]

I don't use macs much, either. :-). The main reason I want to raise this to the TSC its a strategic iceberg floating towards our boat, the TSC should know that node may be uninstallable (unrunnable?) without workarounds on Catalina macs sometime early in 2020, which can perhaps motivate someone to work on this.

[ljharb]

Does this only apply to the installer? or would it also affect version managers like nvm?

[rvagg]

We probably should take further discussion of the details of notarization to nodejs/node#29216.

[Trott]

I'm not actually a macOS user so all of my information on notarization has come secondhand from @AshCripps (who guested at the last Build WG meeting) and @sam-github.

I'd be OK with @AshCripps as a guest too if it makes sense. But if @sam-github has all the context we need and is going to be at the meeting, then cool.

[mhdawson]

I think @sam-github has the context need initial discussion.

[ChALkeR]

I'm at C+L, so I will miss this call.

[mhdawson]

PR for minutes: #774

[Trott]

We used to get @nodejs/moderation team updates in these issues. Would be good to get them again, even if it's just "Nothing to report this week." (I'm pretty sure that some kind of reporting requirement to the TSC and CommComm is actually in the group charter.)

[ryanmurakami]

@Trott Yep, you're right. I've been slacking on this. Would you prefer to have the reports attached to these issues or have me jump on a meeting once a month to report?

Moderation team report from 09/01/19 - 11/07/19

• Received 3 spam/blank emails to report@nodejs.org
• I blocked a user for a trolling/spam comment (https://github.com/nodejs/moderation/issues/297)
• The Moderation team met 10/09. I'll be posting meeting notes to the moderation repo soon

[Trott]

@Trott Yep, you're right. I've been slacking on this. Would you prefer to have the reports attached to these issues or have me jump on a meeting once a month to report?

My personal preference is to have them as comments in these issues. That reaches more people than the meetings (which often get canceled, as they should) and you can tag CommComm and get the report to both groups at once.