Deep dive documents

Open
#439 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reading the four linked Google documents covering Memory Leak, Process Crash, Performance, and Unexpected Behavior. Determine how these documents should be incorporated into the repository; done means the intended deep-dive documentation is present in the project in an agreed location and scope.

Written by the indexing model from the issue text.

Description

never stale
Dominant language
No language data
Stars
550
Forks
69
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.