Node.js Technical Steering Committee (TSC) Meeting 2025-11-05

# Node.js Technical Steering Committee (TSC) Meeting 2025-11-05 ## Links * **Recording**: * **GitHub Issue**: https://github.com/nodejs/TSC/issues/1798 * **Minutes**: https://hackmd.io/@openjs-nodejs/r17AvBWybl ## Present * James Snell @jasnell (voting member) * Chengzhong Wu @legendecas (voting member) * Matteo Collina @mcollina (voting member) * Darshan Sen @RaisinTen (voting member) * Richard Lau @richardlau (voting member) * Ruy Adorno @ruyadorno (voting member) * Joe Sepi @joesepi (Guest - Node.js CPC rep) * 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) * Joyee Cheung @joyeecheung (voting member) * Marco Ippolito @marco-ippolito (voting member) * Filip Skokan @panva (voting member) * Rafael Gonzaga @RafaelGSS (voting member) * Robert Nagy @ronag (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) ## Agenda ### Announcements ### Reminders * Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight) ### CPC and Board Meeting Updates *Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. ### nodejs/TSC * Update charter with communication responsibilities [#1754](https://github.com/nodejs/TSC/pull/1754) - Darshan: does not know how to progress with this as its missing more reviews - James: I have an alternative take on this in [#1756](https://github.com/nodejs/TSC/pull/1756). Darshan PR is too vague and does not cover things we can really influence. My PR is more specific. - Darshan: I'm not sure about this point. - James: [..] we don't need to be in any forum, we don't need admin access. I think Darshan PR is overreaching on what the TSC is. It's not scoped appropriately. - Matteo: Darshan PR prioritize consensus seeking, but marketing by consensus seeking do not work. - James: most of our collaboratos are not marketing professionals and they might not be equipped to make those decisions quickly. - Darshan: We need a framework to collaborate with the Foundation on communication in the Charter. - James: That's why I opened the different PR. - Matteo: considering `the TSC may request administrator or moderator access to ensure representation is aligned with the consensus within the project`, what - Darshan: in that case, we would give us authority to retract/change publicly - Matteo: so the Node.js publicly say A, and then publicly retract B - Darshan: we need to communicate with the party - James: in the past, the question is "who speaks for the project?". Who are the third parties Darshan PR is speaking about? - Matteo: we should seek alignment with the OpenJS Foundation. - James: we don't have a "view" of the project in some matters? When WinterCG was created, we couldn't decide to join it offically on. We have no process to decide who "speaks" for the project. We don't know we are aligned on a topic. This is the fundamental problem. We cannot ask other people to be aligned with us if we don't know. - Darshan: [...] - James: anyone can help with retraction / mistakes happen. We don't need a charter updated for that. - Darshan: if an individual want to post on something, and the Foundation blocks it, can we override it? - James: that seems an individual requirement, there is no consensus about the project on this. It goes back on "how we decide we have alignment between ourselves?". - Darshan: we have a recurring posts on Job seeking, I asked if it could be done some posts that includes Node.js Core work. - James: If we really think there is something that should be talked about, than we do it collectively. It's not adversarial. Discuss the topic. We need to have more conversation with the Foundation. - Darshan: In this case it was more like stalling, it didn't move forward. I don't know if they don't want to do this or not. I would appreciate more collaboration from them. - James: we can't assume there is malicious intent for things not being followed. - Darshan: we should have a process for escalating/asking for these. - James: this is not well defined, how do we resolve it? This is unclear and left undecided. Who has the final say? Some folks thinks the TSC has the final say on all things. The Foundation owns the brand. We have to be clear who is responsible for what. In term of what goes out of the channel, the Foundation has the final say. If we want to have a channel we can control, we should be asking for the Foundation or delegate responsibility to somebody we trust. There are things we need to be clear about. The Foundation is not a 3rd party, they are part of the project. - Darshan: [...] - James: Matteo points out that there is also a gap on the CPC on this topic. - Darshan: I agree. - James: There are gaps, we need them address. - Matteo: Joe, can you help with this? - Joe: We have a CPC working session - Matteo: Tuesday 18th of November - James: how do we make decision on what we want to see? How do we decide what is the message the project wants to communicate. How can we address it? - Darshan: is this blocked by the CPC - Matteo: we had standard-positions in the past, but it was not effective. - Darshan: this is something we could work on the side. - Matteo: I think the marketing team would be reactive to a campaign from the project. - James: The marketing team would not allow self-promotion. Some of those requests that were self-promoting. - Darshan: https://x.com/nodejs/status/1983935272208171399 promotes an indivudal person. - James: that is promoting an initiative we are pushing - Darshan: [...] - James: [...] - Matteo: [...] - James: We could decide as a project to collect funding for an issue. It's a fundamentally different thing for promoting an individual fundraising. ## Strategic Initiatives ## Upcoming Meetings * **Node.js Project Calendar**: <https://nodejs.org/calendar> Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.