unified product and story
Open
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 4k
- Forks
- 339
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 7
Description
- are Nix, Nixpkgs, and NixOS one thing or separate projects?
- see discussion from team meeting NixOS/nix-book#1
- what about Home Manager,
nix-darwin, NixOps, Disnix, Hydra, etc.?- more generally: what do we consider part of the Nix ecosystem for the purpose of documentation?
- should we educate users on the differences or tell a unified story?
- considerations
- scope of required changes
- expertise requirements
- coordination effort
- considerations
- related: NixOS/nix.dev#285 NixOS/nixos-foundation#34
- add decision to roadmap
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 linked team-meeting discussion and related issues NixOS/nix-book#1, nixos-homepage#734, nix.dev#285, and nixos-foundation#34. Resolve whether the ecosystem should be presented as one story or as distinct projects, accounting for scope, expertise, and coordination. Done means the decision is added to the roadmap.
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