Document repository maintainers in description of each repository
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
We should follow the practice of nix-community by clearly stating the maintainers (those with merge permissions) in the description section of each repository. If one of the maintainers does not respond to issues or pull requests, is unreachable, or indicates they will be unavailable for a long time, a new maintainer should be designated from among the contributors promptly. This ensures that contributions to these repositories are not left in a blocked-by-review state.
The format will be like [maintainers=@..., @..., @...]
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 repositories in the NixOS organization and the nix-community practice referenced in the issue. Identify the maintainers with merge permissions for each repository, then update each repository description using the specified [maintainers=@..., @..., @...] format. Done means every repository description states its maintainers and the proposed replacement process is accounted for.
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
- Mostly clear
- Newbie friendliness
- 45/100