Node.js Technical Steering Committee (TSC) Meeting 2022-09-28

[mhdawson]

Time

UTC Wed 28-Sep-2022 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Wed 28-Sep-2022 14:00 (02:00 PM)
US / Mountain	Wed 28-Sep-2022 15:00 (03:00 PM)
US / Central	Wed 28-Sep-2022 16:00 (04:00 PM)
US / Eastern	Wed 28-Sep-2022 17:00 (05:00 PM)
EU / Western	Wed 28-Sep-2022 22:00 (10:00 PM)
EU / Central	Wed 28-Sep-2022 23:00 (11:00 PM)
EU / Eastern	Thu 29-Sep-2022 00:00 (12:00 AM)
Moscow	Thu 29-Sep-2022 00:00 (12:00 AM)
Chennai	Thu 29-Sep-2022 02:30 (02:30 AM)
Hangzhou	Thu 29-Sep-2022 05:00 (05:00 AM)
Tokyo	Thu 29-Sep-2022 06:00 (06:00 AM)
Sydney	Thu 29-Sep-2022 07:00 (07:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2022-09-28&iso=20220928T2100
• or https://www.wolframalpha.com/input/?i=09PM+UTC%2C+Sep+28%2C+2022+in+local+time

Links

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

Agenda

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

nodejs/node

• net: add autoDetectFamily option #44731

nodejs/TSC

• Re-charter the Ecosystem Security WG #1081

Invited

• Antoine du Hamel @aduh95 (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Beth Griggs @BethGriggs (TSC)
• Ruben Bridgewater @BridgeAR (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Danielle Adams @danielleadams (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Geoffrey Booth @GeoffreyBooth (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Chengzhong Wu @legendecas (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Darshan Sen @RaisinTen (TSC)
• Richard Lau @richardlau (TSC)
• Robert Nagy @ronag (TSC)
• Michaël Zasso @targos (TSC)
• Tobias Nießen @tniessen (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.

---

Invitees

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

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

[Trott]

• net: add autoDetectFamily option #44731

This is the only issue (so far) in the agenda. IIUC, the main ask of the TSC is an indication as to whether or not we endorse switching to Happy Eyeballs before 18.x goes LTS. It appears that there is consensus that we should do that. (If you are part of the pro-Happy Eyeballs-in-18.x consensus on the TSC, please leave a 👍. If you are opposed, please leave a comment so that we know that we need more conversation and/or a vote!)

The remaining issues in that PR are about implementation, testing, etc. but even there, there seems to be no controversy. (For example: The change causes two failing tests. That needs to be addressed. No one seems to dispute this.)

Here's the summary of the issue as I understand it. nodejs/node#44731 (comment)

[Trott]

• net: add autoDetectFamily option #44731

This is the only issue (so far) in the agenda. IIUC, the main ask of the TSC is an indication as to whether or not we endorse switching to Happy Eyeballs before 18.x goes LTS. It appears that there is consensus that we should do that. (If you are part of the pro-Happy Eyeballs-in-18.x consensus on the TSC, please leave a 👍. If you are opposed, please leave a comment so that we know that we need more conversation and/or a vote!)

The remaining issues in that PR are about implementation, testing, etc. but even there, there seems to be no controversy. (For example: The change causes two failing tests. That needs to be addressed. No one seems to dispute this.)

Here's the summary of the issue as I understand it. nodejs/node#44731 (comment)

Oh, wait, it's opt-in, right? Yeah, I can't imagine that being controversial, actually. I'm not sure we need anything there other than a few more TSC people chiming in to say, "I like this" or maybe even "What can I do to help?"

[mcollina]

The question for the TSC is if we can enable it by default in v18.

[Trott]

The question for the TSC is if we can enable it by default in v18.

OK, then that is a breaking change, but it is even more of a bug fix than it is a breaking change, and I'm in favor of it.

[Trott]

I've added a tsc-label to #1081. I'll edit this issue and the minutes to include it.

[mhdawson]

PR for minutes - #1289

[Trott]

There was a comment in the chat