Document guidelines around maintainer overload
Open
Nobody has claimed this yet.
content :page_with_curl:
- Dominant language
- R
- Stars
- 164
- Forks
- 69
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 5
Description
Number of packages per person, role of co-maintainer, etc.
Maybe in package curation policies? or collaboration guide?
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 the package curation policies and collaboration guide to determine where guidance on maintainer overload belongs. Clarify the expected guidance for package counts, co-maintainer roles, and related responsibilities, then document the agreed policy in the appropriate guide section.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100