nodejs / nodejs/package-maintenance
Team membership audit
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Hey folks, what do you think about auditing our members to remove those who have been inactive and to see if they still want to remain in this group?
If I don’t receive any objections within a week, I’ll make the list. It would follow the same methodology that was used back in 2022: 30 days to express whether they want to stay or not.
cc: @nodejs/package-maintenance
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
Review issue #497 to understand the referenced audit methodology, then identify the current group membership and the proposed outreach list. Done means completing the 30-day response process and recording which members remain or are removed; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100