Document Nixpkgs committer rules
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
CONTRIBUTING.md covers the case of being a non-committer trying to get code into Nixpkgs. I don't think there's an authoritative place to look for committers who want to know, e.g., how long they should wait before self-merging a PR (on possible penalty of losing bits), or whose reviews are needed before that's okay, or whether it's okay to be a committer and both a Nixpkgs maintainer and the upstream author of a package.
Probably this is because we, as a community, have never really hammered out what those rules are. But if they're going to have teeth, and especially if the teeth get used without trying to work things out ahead of time, I, uh, really want to know where the lines are, for obvious reasons.
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 CONTRIBUTING.md, then read the linked discussions in issues 50 and 121 to understand the unresolved committer-policy concerns. The work is complete when the community agrees on and publishes an authoritative document covering self-merge waiting periods, required reviews, and conflicts involving maintainers and upstream authors.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100