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

[mhdawson]

Time

UTC Wed 22-Nov-2023 19:00 (07:00 PM):

Timezone	Date/Time
US / Pacific	Wed 22-Nov-2023 11:00 (11:00 AM)
US / Mountain	Wed 22-Nov-2023 12:00 (12:00 PM)
US / Central	Wed 22-Nov-2023 13:00 (01:00 PM)
US / Eastern	Wed 22-Nov-2023 14:00 (02:00 PM)
EU / Western	Wed 22-Nov-2023 19:00 (07:00 PM)
EU / Central	Wed 22-Nov-2023 20:00 (08:00 PM)
EU / Eastern	Wed 22-Nov-2023 21:00 (09:00 PM)
Moscow	Wed 22-Nov-2023 22:00 (10:00 PM)
Chennai	Thu 23-Nov-2023 00:30 (12:30 AM)
Hangzhou	Thu 23-Nov-2023 03:00 (03:00 AM)
Tokyo	Thu 23-Nov-2023 04:00 (04:00 AM)
Sydney	Thu 23-Nov-2023 06:00 (06: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-11-22&iso=20231122T1900
• or https://www.wolframalpha.com/input/?i=07PM+UTC%2C+Nov+22%2C+2023+in+local+time

Links

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

Agenda

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

nodejs/node

• lib: promote process.binding/_tickCallback to runtime deprecation #50687
• build: use biome as formatter #50672
• [v18.x] Backport most ESM and customization hook changes #50669
• Seeking approval to use the Node.js logo on the WinterCG website #50668
• doc: move deprecated utils to runtime deprecation #50488
• The env var NODE_V8_COVERAGE intermittently causes the process to hang #49344

nodejs/Release

• proposal for new release schedule / users are not interested in releases that will not become LTS #953

nodejs/TSC

• Update meeting times #1469
• Changes to our nomination process #1467
• Automating Flaky Test Detection #1458

nodejs/admin

• Have a mascot #828
• Create nodejs/socket repository for Node.js implementation of Cloudflare's Socket API #826
• Events / Collaborator Summits for 2024 #814

Invited

• Antoine du Hamel @aduh95 (voting member)
• Yagiz Nizipli @anonrig (voting member)
• Anatoli Papirovski @apapirovski (voting member)
• Benjamin Gruenbaum @benjamingr (voting member)
• Ruben Bridgewater @BridgeAR (voting member)
• Colin Ihrig @cjihrig (voting member)
• Geoffrey Booth @GeoffreyBooth (voting member)
• Gireesh Punathil @gireeshpunathil (voting member)
• James Snell @jasnell (voting member)
• Joyee Cheung @joyeecheung (voting member)
• Chengzhong Wu @legendecas (voting member)
• Matteo Collina @mcollina (voting member)
• Michael Dawson @mhdawson (voting member)
• Moshe Atlow @MoLow (voting member)
• Rafael Gonzaga @RafaelGSS (voting member)
• Darshan Sen @RaisinTen (voting member)
• Richard Lau @richardlau (voting member)
• Robert Nagy @ronag (voting member)
• Ruy Adorno @ruyadorno (voting member)
• Michaël Zasso @targos (voting member)
• Tobias Nießen @tniessen (voting member)
• Beth Griggs @BethGriggs (regular member)
• Ben Noordhuis @bnoordhuis (regular member)
• Сковорода Никита Андреевич @ChALkeR (regular member)
• Shelley Vohr @codebytere (regular member)
• Daniel Bevenius @danbev (regular member)
• Danielle Adams @danielleadams (regular member)
• Franziska Hinkelmann @fhinkel (regular member)
• Gabriel Schulhof @gabrielschulhof (regular member)
• Brian White @mscdex (regular member)
• Myles Borins @MylesBorins (regular member)
• Rod Vagg @rvagg (regular member)
• Tiancheng Timothy Gu @TimothyGu (regular member)
• Rich Trott @Trott (regular member)

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

[GeoffreyBooth]

There are far too many items to resolve in an hour. Can we start with filtering out the ones that are just FYIs and prioritize the ones that need decisions/action? Especially ones that have been on a previous agenda. And maybe find ways to reach decisions async.

[mhdawson]

If people identify ones which are higher priority, I'll make sure to push those to the top of the agenda.

[ronag]

I think nodejs/node#50169 should be on the agenda?

[ronag]

In terms of important I would propose:

#1467
nodejs/node#50169
nodejs/Release#953
nodejs/build#3575

I also think we have a few items on the private agenda.

[mcollina]

I think we might consider start scheduling ad-hoc meetings for some things, because I don't see how we can resolve most of those timely otherwise.

[GeoffreyBooth]

The following I think can be removed from the agenda:

• lib: promote process.binding/_tickCallback to runtime deprecation node#50687 was discussed for an extended period last week and I don’t think it needs more time in a meeting. @joyeecheung suggested a way forward in lib: promote process.binding/_tickCallback to runtime deprecation node#50687 (review) and I think we can either follow that plan or work out revisions to it async.
• build: use biome as formatter node#50672 both isn’t urgent and doesn’t have an obvious question for the TSC to resolve. The PR is only a week old so I think it’s premature for the TSC to step in here when the consensus-seeking process hasn’t had a chance to play out.
• [v18.x] Backport most ESM and customization hook changes node#50669 seems resolved per [v18.x] Backport most ESM and customization hook changes node#50669 (comment).
• Seeking approval to use the Node.js logo on the WinterCG website node#50668 doesn’t have any blocks or obvious open questions, and seems resolved per Seeking approval to use the Node.js logo on the WinterCG website node#50668 (comment). I assume it was added to the agenda as an FYI for us to be aware, but I think we can consider the TSC notified and removed from the agenda unless there’s anything that needs discussion.
• Have a mascot admin#828 seems handled by https://github.com/nodejs/collaborators-public-votes/pull/6.

The following I think should get their own ad hoc meetings with those who are interested, and therefore also be removed from the agenda:

• The env var NODE_V8_COVERAGE intermittently causes the process to hang node#49344 doesn’t have any obvious questions for the TSC to resolve; it’s just a bug that should get fixed. Those knowledgeable about the issue should schedule a time to discuss.
• Proposal for new release schedule / users are not interested in releases that will not become LTS  Release#953 is still in the brainstorming phase, there’s no decision to be made by the TSC yet. This would benefit from a dedicated meeting that includes members of the release team.
• Update meeting times #1469 should get a meeting to discuss the question of how to decide meeting times moving forward; but I think that should wait until after we see what our current process produces for the new times. If people are happy with what we get, maybe there’s no need to change anything.
• Changes to our nomination process #1467 feels like it should be discussed in a private meeting.
• Create nodejs/socket repository for Node.js implementation of Cloudflare's Socket API admin#826 feels like it should be discussed in a meeting with those familiar with the topic.
• Events / Collaborator Summits for 2024 admin#814 feels like something that could either be discussed async on that thread or in a dedicated meeting.

The following I think should just be acted upon:

• util: move deprecated utils to runtime deprecation node#50488 is blocked by @ronag who has been unresponsive for three weeks to entreaties for seeking consensus. I think the block should simply be dismissed, as per our policy in https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md#objections it’s been more than seven days.
• Automating Flaky Test Detection build#3575 doesn’t have an obvious question for the TSC, other than “should we let this company see if they can improve our CI?” To which I feel like, this is a question for the build team and I’m happy with whatever they decide.

So what’s left?

• Private stuff
• deps,doc,lib,src,test: add experimental web storage node#50169

[mhdawson]

@GeoffreyBooth thanks for the summary/overview, I pulled in your suggestions into the doc https://docs.google.com/document/d/1er2sOU4UE-f6wWuBuQHD6jwPjVva2sOUDhItxWKH0uE/edit to capture minutes and I think we can strart with deps,doc,lib,src,test: add experimental web storage node#50169 and then if we have time before private session (45 mins) we can quickly go through th others.

[mhdawson]

PR for minutes - #1475