nodejs / nodejs/TSC

Node.js Technical Steering Committee (TSC) Meeting 2026-04-15

Open
#1,849 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tsc-meeting
Dominant language
JavaScript
Stars
694
Forks
142
PR merge metrics
No merged PRs in 30d

Description

Time

UTC Wed, Apr 15, 2026, 01:00 PM:

Timezone Date/Time
US / Pacific Wed, Apr 15, 2026, 06:00 AM
US / Mountain Wed, Apr 15, 2026, 07:00 AM
US / Central Wed, Apr 15, 2026, 08:00 AM
US / Eastern Wed, Apr 15, 2026, 09:00 AM
EU / Western Wed, Apr 15, 2026, 02:00 PM
EU / Central Wed, Apr 15, 2026, 03:00 PM
EU / Eastern Wed, Apr 15, 2026, 04:00 PM
Moscow Wed, Apr 15, 2026, 04:00 PM
Chennai Wed, Apr 15, 2026, 06:30 PM
Hangzhou Wed, Apr 15, 2026, 09:00 PM
Tokyo Wed, Apr 15, 2026, 10:00 PM
Sydney Wed, Apr 15, 2026, 11:00 PM

Or in your 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
  • 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/node
  • 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified; start with the meeting time, agenda links, and the referenced Minutes page. Done means the meeting information, agenda, and participation details are current and the meeting record is maintained.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
developer-experience
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.