nodejs / nodejs/next-10

Node.js Next 10 Years team Meeting 2026-09-16

Open
#399 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
550
Forks
31
Avg merge
4h 27m
Merged PRs (30d)
1

Description

Time

UTC Wed, Sep 16, 2026, 02:00 PM:

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

Or in your local time:

Links

Invited

  • Next 10 years team: @nodejs/next-10
Observers/Guests

None.

Agenda

Issues and Pull Requests

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

nodejs/next-10
  • Review & update Technical Priorities #390

Joining the meeting


Invitees

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

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure

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

Start by reading the meeting details in this issue, the linked HackMD minutes, and the referenced next-10 issue #390. The payload does not identify a code file or implementation task; completion is tied to keeping this meeting record, agenda, links, and invitee information accurate.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.