Node.js QUIC Team Meeting 2026-09-17

Open
#65,972 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
node.js
Domain
documentation

Research direction

Start with the meeting time, the QUIC team invitees, the agenda entry for nodejs/node#65314, and the linked HackMD minutes. This issue describes a scheduled team meeting rather than a code change; it is complete when the meeting and its associated minutes are handled.

Written by the indexing model from the issue text.

Description

Time

UTC Thu, Sep 17, 2026, 03:00 PM:

Timezone Date/Time
US / Pacific Thu, Sep 17, 2026, 08:00 AM
US / Mountain Thu, Sep 17, 2026, 09:00 AM
US / Central Thu, Sep 17, 2026, 10:00 AM
US / Eastern Thu, Sep 17, 2026, 11:00 AM
EU / Western Thu, Sep 17, 2026, 04:00 PM
EU / Central Thu, Sep 17, 2026, 05:00 PM
EU / Eastern Thu, Sep 17, 2026, 06:00 PM
Moscow Thu, Sep 17, 2026, 06:00 PM
Chennai Thu, Sep 17, 2026, 08:30 PM
Hangzhou Thu, Sep 17, 2026, 11:00 PM
Tokyo Fri, Sep 18, 2026, 12:00 AM
Sydney Fri, Sep 18, 2026, 01:00 AM

Or in your local time:

Links

Invited

  • @nodejs/quic
Observers/Guests

None.

Agenda

Issues and Pull Requests

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

nodejs/node
  • Request for early feedback: Fetch server API #65314

Joining the meeting


Invitees

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

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure
Dominant language
JavaScript
Stars
122k
Forks
37.4k
Avg merge
4d 3h
Merged PRs (30d)
273

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.

More from nodejs/node

All issues in nodejs/node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.