Node.js Technical Steering Committee (TSC) Meeting 2024-06-05

[mhdawson]

Time

UTC Wed 05-Jun-2024 14:00 (02:00 PM):

Timezone	Date/Time
US / Pacific	Wed 05-Jun-2024 07:00 (07:00 AM)
US / Mountain	Wed 05-Jun-2024 08:00 (08:00 AM)
US / Central	Wed 05-Jun-2024 09:00 (09:00 AM)
US / Eastern	Wed 05-Jun-2024 10:00 (10:00 AM)
EU / Western	Wed 05-Jun-2024 15:00 (03:00 PM)
EU / Central	Wed 05-Jun-2024 16:00 (04:00 PM)
EU / Eastern	Wed 05-Jun-2024 17:00 (05:00 PM)
Moscow	Wed 05-Jun-2024 17:00 (05:00 PM)
Chennai	Wed 05-Jun-2024 19:30 (07:30 PM)
Hangzhou	Wed 05-Jun-2024 22:00 (10:00 PM)
Tokyo	Wed 05-Jun-2024 23:00 (11:00 PM)
Sydney	Thu 06-Jun-2024 00:00 (12:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2024-06-05&iso=20240605T1400
• or https://www.wolframalpha.com/input/?i=02PM+UTC%2C+Jun+05%2C+2024+in+local+time

Links

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

Agenda

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

nodejs/node

• module: allow module.register from workers #53200
• src: make --env-file return warning when not found #53177

nodejs/nodejs.org

• Require TSC approval for stances #6772

nodejs/TSC

• Module customization hooks and worker threads #1566
• Open OpenCollective and Github Sponsors for Node.js #1553
• Coordinating nodejs security audit report finalization and publication #1546

nodejs/next-10

• Next 10 - Funding Deep Dive #273

Invited

• Antoine du Hamel @aduh95 (voting member)
• Anatoli Papirovski @apapirovski (voting member)
• Benjamin Gruenbaum @benjamingr (voting member)
• Ruben Bridgewater @BridgeAR (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)
• Marco Ippolito @marco-ippolito (voting member)
• Matteo Collina @mcollina (voting member)
• Michael Dawson @mhdawson (voting member)
• Moshe Atlow @MoLow (voting member)
• Rafael Gonzaga @RafaelGSS (voting member)
• Richard Lau @richardlau (voting member)
• Robert Nagy @ronag (voting member)
• Ruy Adorno @ruyadorno (voting member)
• Paolo Insogna @ShogunPanda (voting member)
• Michaël Zasso @targos (voting member)
• Tobias Nießen @tniessen (voting member)
• Beth Griggs @BethGriggs (regular member)
• Ben Noordhuis @bnoordhuis (regular member)
• Colin Ihrig @cjihrig (regular member)
• Shelley Vohr @codebytere (regular member)
• Danielle Adams @danielleadams (regular member)
• Myles Borins @MylesBorins (regular member)
• Rich Trott @Trott (regular member)
• Yagiz Nizipli @anonrig (regular member)
• Joe Sepi @[email protected] (Guest - Node.js CPC rep)

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

[benjamingr]

module: allow module.register from workers
Module customization hooks and worker threads

These seem like the same issue, right? What specific feedback do we want from the TSC @mcollina @GeoffreyBooth ?

It looks like you did a good job of identifying issues, working on a revert for the current major (and revert revert for right after) + have ideas on how to enable the use case while keeping the technical win of a single loader thread.

Anything other than "the TSC is happy you were all proactive on this and came to an agreement"?

[MoLow]

nodejs/tap2junit#56 can be removed from the agenda for now

[mcollina]

I'll do my best to join but I might not be able to.

[mhdawson]

@MoLow removed. Also removed the Abassador program issue as its been on the TSC agenda long enough as an FYI.

[jasnell]

This hits right in the middle of conflicting call. I'll weigh in on various issues in-thread where appropriate

[GeoffreyBooth]

These seem like the same issue, right? What specific feedback do we want from the TSC @mcollina @GeoffreyBooth ?

They’re the same issue. I think the only question for the TSC is if we’re okay with shipping the 22.1.0 behavior for this as 22.3.0, when we know it’s going to change yet again; though I don’t think we have any other choice at this point unless we want to delay the 22.3.0 release. So I guess at this point it’s more of an FYI.

[mhdawson]

PR for minutes - #1567