NixOS / NixOS/org

project domain name

Open
#80 24 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
48
Forks
36
Avg merge
2m
Merged PRs (30d)
3

Description

we observe that people are confused about names in the Nix ecosystem and find it hard to distinguish between its components.

given the goal of easing learning Nix, we should reduce that confusion as much as possible.

proposal:

  • match domain names to component names

considerations:

  • Nix and Nixpkgs are not used separately at large
    • its possible though and some do it
  • NixOS covers a distinct use case, and only ~half of the 2022 survey respondents use NixOS daily
    • @MMesch reports that most business users are not on NixOS
  • Nix is at the core of the ecosystem, everything builds on top and around it

current state:

options:

  • use nixpkgs.org for Nix+Nixpkgs (current web site), redirect nixos.org to NixOS/nixpkgs/tree/master/nixos
    • contributors more focused on NixOS could set up something more appropriate on their own
  • use nix.dev
    • with support from @domenkozar
    • done, but currently only for the purpose of serving a documentation resource
  • buy nix.org
    • with support from Foundation (@edolstra @domenkozar @thufschmitt @grahamc)
  • more domain names

related:

@garbas this is a responsibility of the marking team, but intimately concerns documentation w.r.t. consistency and avoiding confusion

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current nixos.org site and the listed domain states, then read the related NixOS/nix.dev#290 and nixos-homepage#633 discussions. Compare the proposed domain arrangements and linked survey and discussion context; done means the project has a decided, consistent mapping between domains and Nix ecosystem components.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.