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

Ouverte
#1,910 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
1/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
node.js
Domaine
documentation

Piste de recherche

This issue schedules a Node.js Technical Steering Committee meeting and lists its agenda, invitees, and joining links. Start by checking the meeting minutes link and the listed agenda items; the issue does not request a code or documentation change, so there is no contributor task with a completion criterion.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Time

UTC Wed, Nov 11, 2026, 01:00 PM:

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

Or in your local time:

Links

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)
  • 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

None.

Agenda

Issues and Pull Requests

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

nodejs/TSC
  • Self-nominate for security release steward #1911
  • GSoC 2027 #1909
  • Enroll nodejs/node in Anthropic OSS Scanner project? #1905
  • Proposal: use Node.js sponsorship funds for additional CI/build capacity on Hetzner #1903
  • doc: adds web wg #1888
  • Draft Statement of Work - Test reliability lead #1629
nodejs/admin
  • Nominations for OpenJS CPC voting members #1106
  • doc: update Code of Conduct to Contributor Covenant 3.0 #1097
  • Proposal: Add a more explicit incident response lifecycle to the Moderation Policy #1096
  • Configure pull request limit for users without write access #1084
nodejs/node
  • Proposal: build official Node.js binaries for glibc-based Linux using PIE, enables ASLR, helps prevent RCE #66951
  • doc: move to redesign #66713
  • lib: add built-in OpenTelemetry tracing #66587
  • What will Domain be replaced with? #10843
nodejs/undici
  • Undici WG meeting: let's fix our governance so we can resolve our disagreements #5989
  • option to disable permessage-deflate #5447
nodejs/web-team
  • doc: adds Charter #182

Joining the meeting


Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure
Langage dominant
JavaScript
Étoiles
693
Forks
142
Merge moyen
22 h 52 min
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/TSC

Toutes les issues de nodejs/TSC

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.