Node.js Technical Steering Committee (TSC) Meeting 2023-02-22

[mhdawson]

Time

UTC Wed 22-Feb-2023 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Wed 22-Feb-2023 13:00 (01:00 PM)
US / Mountain	Wed 22-Feb-2023 14:00 (02:00 PM)
US / Central	Wed 22-Feb-2023 15:00 (03:00 PM)
US / Eastern	Wed 22-Feb-2023 16:00 (04:00 PM)
EU / Western	Wed 22-Feb-2023 21:00 (09:00 PM)
EU / Central	Wed 22-Feb-2023 22:00 (10:00 PM)
EU / Eastern	Wed 22-Feb-2023 23:00 (11:00 PM)
Moscow	Thu 23-Feb-2023 00:00 (12:00 AM)
Chennai	Thu 23-Feb-2023 02:30 (02:30 AM)
Hangzhou	Thu 23-Feb-2023 05:00 (05:00 AM)
Tokyo	Thu 23-Feb-2023 06:00 (06:00 AM)
Sydney	Thu 23-Feb-2023 08:00 (08:00 AM)

Or in your local time:

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

Links

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

Agenda

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

nodejs/node

• doc: add request to hold off publicising sec releases #46702
• Request: mark test runner stable in Node 20.0.0 #46642
• stream: bump default highWaterMark #46608
• Confused setTimout behaviour in NodeJS #46596
• net: rework autoSelectFamily implementation #46587

nodejs/TSC

• Moving away from Team Discussions #1340
• Proposal: drop mandatory meeting attendance requirement #1338

nodejs/admin

• Website migration to Vercel #766

nodejs/llhttp

• Handle extra spaces in status line #216

nodejs/next-10

• Metadata Proposal for Docs #166

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)
• Rafael Gonzaga @RafaelGSS (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

[mhdawson]

PR for minutes - #1346

[GeoffreyBooth]

Sorry, somehow my calendar didn’t alert me to this. Re making the test runner stable, there are a few TODO items on that issue thread that I think need to get done before we can go ahead and do it. Basically, surveying all the test runner features and identifying any where we might want to make breaking changes sooner than semver-major, and ensuring that we will still be able to because those areas would remain behind an experimental flag. With the bulk of the feature becoming stable, I think it’s important that the unstable parts need a flag to use so that users are fully aware when they’re deviating from the stable path. And maybe there are none, but I haven’t seen anyone put together a list or respond to those questions on the thread. Once that work is done, then I think we’re all in agreement that the feature is ready to become stable.