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

[mhdawson]

Time

UTC Wed 15-Nov-2023 15:00 (03:00 PM):

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1mTH7W6ohxZdlJo1cxN4fERsFLVzdj8Ed0CrQV2Nw9G0/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
• [v18.x] Backport most ESM and customization hook changes #50669
• doc: move deprecated utils to runtime deprecation #50488
• test: set test-fs-watch as flaky #50250
• deps,doc,lib,src,test: add experimental web storage #50169
• The env var NODE_V8_COVERAGE intermittently causes the process to hang #49344
• Support for file-system based persistent code cache in user-land module loaders #47472

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

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

[cjihrig]

deps,doc,lib,src,test: add experimental web storage nodejs/node#50169

I won't be able to attend this week, but it would be good if the TSC could decide one way or the other if this is something we want in core. There has been a block on that PR for over a month. That particular block is not going to be resolved on its own. This comment summarizes many of the questions related to the PR.

[GeoffreyBooth]

The agenda is pretty long, perhaps we could prioritize the items where decisions need to be made? That sounds like #50169, any others? And could you spell out what specific questions you want answered? For some like nodejs/node#47472 and nodejs/node#50669 it’s not obvious.

[anonrig]

We can nodejs/node#50250 from agenda

[joyeecheung]

I think the question for nodejs/node#47472 is, whether the security vector of "potentially allowing the modification of any module (which requires bytecode reverse-engineering) via an environment variable for whoever that controls the file system" are big enough a concern to not implement a fs-backed code cache support in loaders nodejs/node#47472 (comment)

[GeoffreyBooth]

I think the question for nodejs/node#47472 is, whether the security vector of “potentially allowing the modification of any module (which requires bytecode reverse-engineering) via an environment variable for whoever that controls the file system” are big enough a concern to not implement a fs-backed code cache support in loaders nodejs/node#47472 (comment)

Reading that thread I don’t really see anyone saying that we shouldn’t build the feature, just @bnoordhuis warning that it could have security implications. But it’s not clear (at least to me) what those security concerns really are, or how they’re any worse than anything else we currently allow, so I don’t consider the proposal blocked or needing TSC input. I think it’s safe to proceed to PR and if concrete security issues emerge in that PR we can address them then, but I think it’s likely enough that a workable PR will succeed that it’s worth investing the effort.

[joyeecheung]

The motivation of bringing it to TSC is to see if anyone else have concerns, to prevent late surprises on theoretical grounds when the PR is actually made.

[benjamingr]

I won't be able to attend this week, but it would be good if the TSC could decide one way or the other if this is something we want in core.

I left a bunch of questions a wile ago in nodejs/node#50169 (comment) , I think for the TSC to decide those would need to be reasonably answered.

[mhdawson]

PR for minutes - #1472