nodejs / nodejs/package-maintenance

[Support Levels] Blog outlining levels and how to use our team's tool to validate them

Open
#223 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

article
Dominant language
No language data
Stars
423
Forks
147
PR merge metrics
No merged PRs in 30d

Description

This is related to next steps on issue https://github.com/nodejs/package-maintenance/issues/192, "Next steps on Support levels in Package.json"

The issue title is a bit of a misnomer since the team seems to have decided at the conference (with input from the larger group) that it would be better to keep the support level info to a separate file rather than adding to the package.json file.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.