nodejs / nodejs/package-maintenance
[key packages] High Impact Packages
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Split 2/3 of #105
We have to to choose a larger group of high impact packages to implement the same practices and standards developed in conjunction with the Pilot Packages.
To choose this group of packages, we need to define the right formula to find who need help first.
The starting list of criteria for ranking is:
➕ = higher value increment the priority assigned
➖ = lower value increment the priority assigned
| Criteria | Evaluation for priority |
|---|---|
| Number of downloads | ➕ |
| Number of downloads of their full dependency tree✨ | ➕ |
| Most depended-upon packages | ➕ |
| Number of dependencies | ➖ |
| Test against Node.js versions | ➕, less is to seek and understand why |
| Old dependencies | Less are to seek and understand why. "old" is managable or do we have many false positive? |
| Deprecated dependencies | ➖ |
| Open issues | ➕ - only if labelled as confirmed bug or bug |
| Is it maintained by a company? | They want help? |
| Last activities | More recent: ➕ |
✨ During this process, we should also check if one of those dependency is on an older major and why.
What to discuss here
- We need to complete the criteria list and define the evaluation of the criteria itself
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #105 and the criteria table in this issue. Define the remaining criteria and how each should affect package priority, including the questions about dependencies, maintenance, and Node.js versions. Done means the criteria list and evaluation formula are agreed upon for selecting high-impact packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100