Skip to content

2026-03-18.md

Latest commit

 

History

History
80 lines (56 loc) · 3.69 KB

2026-03-18.md

File metadata and controls

80 lines (56 loc) · 3.69 KB

Node.js Technical Steering Committee (TSC) Meeting 2026-03-18

Links

Present

  • Antoine du Hamel @aduh95 (voting member)
  • Matteo Collina @mcollina (voting member)
  • Filip Skokan @panva (voting member)
  • Robert Nagy @ronag (voting member)
  • Michaël Zasso @targos (voting member)
  • Marco Ippolito @marco-ippolito (voting member)

Agenda

Announcements

  • Node.js Interactive as part of RenderATL.
  • Collab summit is going ahead, submit your sessions
  • Security release coming up next week for all release lines

Reminders

CPC and Board Meeting Updates

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

  • ESP extension was launched with Node Source to promote upgrades.
  • Board meeting scheduled for next week
  • CoC Covenant 3.0 approved

nodejs/TSC

  • Vote on AI contributions #1831
    • Matteo: Discussion on the 1st of April to allow friendly US-timezones. Vote starting afterwards.
    • Matteo: AI-assisted engineering policy on the agenda for the OpenJS Board (meeting of the 27th).
    • Filip: there are misleading titles floating around related to this.
    • Matteo: I will do some comms around the topic.
  • 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

  • Creating rust team #1047

    • no objections for two weeks

  • Ownership of Rust crates #1045

    • Antoine: Currently Node.js has no plan to use merve from Cargo / Rust. So adding a Rust pipeline increase our maintainership burden.

  • Transfer DataDog/dc-polyfill to the org #1019

    • Already approved, removed form TSC agenda.

nodejs/node

  • doc: create ai-guidelines and include to CONTRIBUTING #62105
  • tools: add ncrypto updater script #61613
    • Filip: Antoine expressed the opinion that both approaches are sound, and see if the flow nodejs->ncrypto is feasible.
    • Antoine: the flow ncrypto->node will be much simpler
    • Filip: we could have automation run when a new version of Node.js is cut to open a PR to ncrypto automatically.
    • Marco: moving ncrypto first will makes security releases harder. It would be easier to keep it in core to avoid additional coordination.
    • Matteo: We should have the people benefitting from it in the call to discuss.
    • Antoine: why ..
    • Filip: there are only a few events that needs ncrypto changes, but it would be really annoying for contributing to Node.js. It's easier for the consumers of ncrypto to float their patches on top. It never made sense from Node.js.
    • Matteo: I would recommend James to host a session on ncrypto to resolve this at the collab summit.
  • Virtual File System for Node.js #61478

Strategic Initiatives

Upcoming Meetings

Click Add to Google Calendar at the bottom left to add to your own Google calendar.