Repository navigation
Node.js Technical Steering Committee (TSC) Meeting 2025-06-25 #1752
Description
Time
UTC Wed 25-Jun-2025 13:00 (01:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 25-Jun-2025 06:00 (06:00 AM) |
| US / Mountain | Wed 25-Jun-2025 07:00 (07:00 AM) |
| US / Central | Wed 25-Jun-2025 08:00 (08:00 AM) |
| US / Eastern | Wed 25-Jun-2025 09:00 (09:00 AM) |
| EU / Western | Wed 25-Jun-2025 14:00 (02:00 PM) |
| EU / Central | Wed 25-Jun-2025 15:00 (03:00 PM) |
| EU / Eastern | Wed 25-Jun-2025 16:00 (04:00 PM) |
| Moscow | Wed 25-Jun-2025 16:00 (04:00 PM) |
| Chennai | Wed 25-Jun-2025 18:30 (06:30 PM) |
| Hangzhou | Wed 25-Jun-2025 21:00 (09:00 PM) |
| Tokyo | Wed 25-Jun-2025 22:00 (10:00 PM) |
| Sydney | Wed 25-Jun-2025 23:00 (11:00 PM) |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2025-06-25&iso=20250625T1300
- or https://www.wolframalpha.com/input/?i=01PM+UTC%2C+Jun+25%2C+2025+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/119T3kHRTe6EWmgAggtYqg_tSyTdVcvVgnrgkzLW7-8s/edit
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- meta: add ability to block issues #58796
- Remove
Symbol.disposeintegration insetTimeoutandsetInterval#58689 - Update npm to v11 in Node.js v22 #58423
nodejs/nodejs.org
- Revert ESP related changes #7884
- chore(homepage): link to our blog, rather than HeroDevs #7883
- Add blog post publishing guidelines #7860
- HeroDevs ESP Visibility Improvements #7773
nodejs/TSC
- Let's talk about the CI situation #1614
nodejs/admin
- Proposal: Social Communication Plan #977
nodejs/bluesky
- Starting a poll for feedback from Bluesky followers about content curation of the official Bluesky account #128
Invited
- Antoine du Hamel @aduh95 (voting member)
- Yagiz Nizipli @anonrig (voting member)
- Benjamin Gruenbaum @benjamingr (voting member)
- Ruben Bridgewater @BridgeAR (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)
- Filip Skokan @panva (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)
- 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)
- Geoffrey Booth @GeoffreyBooth (regular member)
- Moshe Atlow @MoLow (regular member)
- Shelley Vohr @codebytere (regular member)
- Rich Trott @Trott (regular member)
- Joe Sepi @joesepi (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
Activity
jasnell commentedon Jun 25, 2025
I'm not sure I'll be able to make the meeting today due to conflicts so I want to comment on these issues here:
I'm strongly -1 on removing the link.
I'm strongly and firmly -1 on nodejs/nodejs.org#7884 but I'm not going to block the PR because sometimes it's counterproductive to try stopping people from acting against their own best interests.
I personally find the behavior and attitudes of certain TSC members throughout this discussion has been terrible, counterproductive, and not serving the best interests of the project, and in my opinion are counter to published TSC member expectations.
Although certain TSC members have tried to cast this as an issue of transparency and having private meetings that's not actually the issue here and I'll ask those folks to stop conflating and confusing the issues. Trying to use this issue to try to force a particular unrelated agenda is inappropriate and counterproductive. (Mentioning this because it keeps being raised -- inappropriately in my opinion -- in the discussion threads for the above topics).
As for the claim in issue nodejs/nodejs.org#7773 that governance policy was ignored, I believe at this point that's been thoroughly debunked in the discussions. The governance process was followed even if there was a breakdown in communication about it. I would further just remind TSC members that our member expectations have very clear guidelines about not running off the social media to air grievances and instead strive to work in good faith within the project to resolve issues.
The TSC has known about the requirements to include a link to the program as a condition of the program for many months with no prior objections raised. (It was mentioned and discussed several times and was clearly stated explicitly in the presentations the Foundation gave to the TSC briefing about this program with no objections raised that I can recall.
mhdawson commentedon Jun 25, 2025
PR for minutes - #1753