Add "who builds Nix and NixOS?" to FAQ
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 4k
- Forks
- 339
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 7
Description
Observations
It's not clear to newcomers that "NixOS" is both an OS and an organization, and that "NixOS" also manages "Nix".
I'm new to Nix, and I found it very confusing. I skimmed through the docs, but it only left me more confused when the "How to get help" section in the nix.dev documentation linked me to the NixOS forums.
Problem
I think the "normal" assumption for newcomers is that nix was created and then some other project was created (by other people) that included nix as their package manager in a new distro called NixOS.
I think it's very confusing why the FAQ tells users to go to the NixOS forums to ask questions about nix.
The FAQ doesn't indicate the relationship between nix, NixOS, or all the other nix-related software projects in this ecosystem.
Approaches
I think we should add questions to the FAQ that address this. For example:
- What is the relationship between nix and NixOS?
- What other projects are managed by NixOS?
- What other, similar projects that are not managed by NixOS?
To make this clear, I think any TLD domains that are paid for by NixOS should be clearly enumerated, so new users know what's official and what's not.
Willing to help?
Yes. If a PR is welcome, let me know and I'll submit one.
Priorities
Add 👍 to issues you find important.
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 the nix.dev FAQ and its “How to get help” section, then read the linked Discourse discussion about the relationship between Nix and NixOS. Done means the FAQ clearly explains NixOS, Nix, related projects, and which projects or domains are official.
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
- 42/100