Node.js Technical Steering Committee (TSC) Meeting 2026-04-29
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 694
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Time
UTC Wed, Apr 29, 2026, 10:00 AM:
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed, Apr 29, 2026, 03:00 AM |
| US / Mountain | Wed, Apr 29, 2026, 04:00 AM |
| US / Central | Wed, Apr 29, 2026, 05:00 AM |
| US / Eastern | Wed, Apr 29, 2026, 06:00 AM |
| EU / Western | Wed, Apr 29, 2026, 11:00 AM |
| EU / Central | Wed, Apr 29, 2026, 12:00 PM |
| EU / Eastern | Wed, Apr 29, 2026, 01:00 PM |
| Moscow | Wed, Apr 29, 2026, 01:00 PM |
| Chennai | Wed, Apr 29, 2026, 03:30 PM |
| Hangzhou | Wed, Apr 29, 2026, 06:00 PM |
| Tokyo | Wed, Apr 29, 2026, 07:00 PM |
| Sydney | Wed, Apr 29, 2026, 08:00 PM |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2026-04-29&iso=20260429T100000
- or https://www.wolframalpha.com/input/?i=10%3A00%20AM+UTC%2C+Apr%2029%2C%202026+in+local+time
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting. (Updated daily)
nodejs/TSC
- Reconsider ABI stability requirement for V8 updates in majors #1852
- Update meeting schedule #1832
- Vote on AI contributions #1831
- Update charter with communication responsibilities #1754
- Self-serve model for funding Node.js work #1747
- Draft Statement of Work - Test reliability lead #1629
nodejs/admin
- Clean up triager team #1058
nodejs/node
- JSON Schema validation in Node.js core #62598
- loader: implement package maps #62239
- doc: create ai-guidelines and include to CONTRIBUTING #62105
- tools: add ncrypto updater script #61613
- Virtual File System for Node.js #61478
- lib: added logger api in node core #60468
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)
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the meeting time, Links, Agenda, and Notes sections in this issue, then review the linked HackMD minutes. There is no implementation task or named file to change; the post is complete as a meeting announcement and agenda.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100