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

Offen
  • Stimmt etwas nicht?
#1,910 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
1/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
node.js
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
JavaScript
Sterne
693
Forks
142
Ø Merge
22 Std. 52 Min.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nodejs/TSC

Alle Issues in nodejs/TSC

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.