[2026 June] Regular manual review
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
Because the documentation in this repository may slowly deviate from reality, this monthly issue is created to regularly review the files.
All files are listed below with their associated code owners, who are asked to ensure that their contents match reality.
-
If that's not the case, please investigate how this happened and address it so that it doesn't happen again.
To mitigate an inconsistency:
- If a PR was merged without updating reality, update reality to match the new documentation, then post a comment in this issue with what was done.
- If reality was updated without a PR, open a PR to update the documentation, then post a comment in this issue with a link to the PR.
-
Once the documentation matches reality, tick the checkmark.
If all checkmarks are ticked, the issue can be closed.
Files
These are the current code owners for each file:
-
calendar.md: @tomberek @cafkafk @infinisil -
constitution.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
discourse.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) @mweinelt @lassulus @jtojnar @ctheune @dpausp -
freescout.md: @infinisil -
github-org-owners.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
github.md: @NixOS/org (@zimbatm @tomberek @Lassulus @infinisil @winterqt) -
governance.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
hetzner.md: @NixOS/infra (@Mic92 @mweinelt @jfly @arianvp @vcunat) -
mail.md: @NixOS/infra (@Mic92 @mweinelt @jfly @arianvp @vcunat) -
matrix.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
moderation.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
nixcon.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
nixos-releases.md: @NixOS/nixpkgs-core (@alyssais @emilazy) -
nixpkgs-committers.md: @NixOS/nixpkgs-core (@alyssais @emilazy) -
nixpkgs-core.md: @NixOS/nixpkgs-core (@alyssais @emilazy) -
org-repo.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
resources.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
values.md: @NixOS/steering (@philiptaron @tomberek @K900 @roberth @Ericson2314 @JulienMalka @cafkafk) -
vault.md: @Mic92 @mweinelt@zimbatm
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 by reading the unchecked files under doc/ and the linked CODEOWNERS entry to identify the responsible context; discourse.md also points to issue 262. Compare each document with current project reality, then update documentation or open a PR as appropriate, report the result in this issue, and tick the matching checks when all reviewed content is accurate.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100