Node.js Diagnostics WorkGroup Meeting 2025-12-25

Open
#675 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the meeting time, the Minutes link, and the listed nodejs/node agenda issue. No source file or test entry point is mentioned, and the issue does not describe a code or documentation change; it is complete only as a meeting announcement and agenda record.

Written by the indexing model from the issue text.

Description

Time

UTC Thu, Dec 25, 2025, 05:00 PM:

Timezone Date/Time
US / Pacific Thu, Dec 25, 2025, 09:00 AM
US / Mountain Thu, Dec 25, 2025, 10:00 AM
US / Central Thu, Dec 25, 2025, 11:00 AM
US / Eastern Thu, Dec 25, 2025, 12:00 PM
EU / Western Thu, Dec 25, 2025, 05:00 PM
EU / Central Thu, Dec 25, 2025, 06:00 PM
EU / Eastern Thu, Dec 25, 2025, 07:00 PM
Moscow Thu, Dec 25, 2025, 08:00 PM
Chennai Thu, Dec 25, 2025, 10:30 PM
Hangzhou Fri, Dec 26, 2025, 01:00 AM
Tokyo Fri, Dec 26, 2025, 02:00 AM
Sydney Fri, Dec 26, 2025, 04:00 AM

Or in your local time:

Links

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting. (Updated daily)

nodejs/node
  • Port/Duplicate async_hooks tests to use AsyncLocalStore #55712

Invited

  • Diagnostics team: @nodejs/diagnostics
Observers/Guests

Notes

The agenda comes from issues labelled with diag-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Dominant language
No language data
Stars
550
Forks
69
PR merge metrics
No merged PRs in 30d

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/diagnostics

All issues in nodejs/diagnostics

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.