nodejs / nodejs/package-maintenance
[key packages] Addressing Node.js CITGM failures
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
This was brought up in the 2019-09-24 meeting issue by @Trott:
Not sure if this fits in with the package-maintenance team's goals/charter/whatever, but assistance getting things aligned in the ecosystem and Node.js 13.0.0 such that we minimize the pain of any Node.js breaking changes for end users would be 💯. Specifically, it would be great if we could get rid of as many CITGM issues there as possible.
We didn't really get a chance to discuss this during the meeting, so creating a separate issue for this:
- What can we as part of this group do to help out on v13 and future releases?
- How can package maintainers get involved?
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 reading the linked 2019-09-24 meeting issue and the CITGM issues referenced in the Node.js pull request comment. Determine which package failures and Node.js 13 compatibility work are in scope, then review how package maintainers could participate. Done would require an agreed, actionable plan for addressing the failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100