nodejs / nodejs/package-maintenance
PMWG/pkgjs Year In Review Blog Post
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
It is important to celebrate the wins, and this year I think the PMWG did a lot. I think it would be great if we could put together a little post to share what we accomplished this year and appeal to new folks who might like to participate. To get the conversation started, here is a list of things we have worked on (will be updated as folks comment with more):
- pkgjs org setup (a place to work on these tools)
- wiby
- Support spec tooling
Once we have a list of topics, @mhdawson recommended (and I really like the idea) that we break up the sections so others can write them to split up the work. Does this approach sound good to everyone?
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 with the proposed accomplishments in the issue, including pkgjs org setup, wiby, and support spec tooling, and review the discussion context as it develops. Done means agreeing on the topics and section ownership, writing the year-in-review post, and preparing it for sharing with prospective contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100