project domain name

[fricklerhandwerk]

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:

• nixos.org used for everything
• nixpkgs.org redirects to NixOS/nixpkgs
• nix.store currently redirects to nixos.org
• nix.dev is a separate project owned by @domenkozar, contents used on nixos.org/learn without attribution
  nix.dev is an official documentation resource
• nix.org is currently being squatted on

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:

• unified product and story nix.dev#290
• Figure out a pattern to break-out a NixOS Linux distribution "sub-site" (again) nixos-homepage#633

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

[asymmetric]

On buying nix.org, I think a good (and way cheaper) alternative could be buying nix-lang.org. It's what many other languages do.

[fricklerhandwerk]

The Nix ecosystem and the Nix package manager are not really about the Nix language (just as Bazel is not really about Starlark). nix-lang.org would easily make the impression the project is somehow revolving around the configuration language. That would defeat the purpose of reducing confusion.

[asymmetric]

I disagree. Part of the confusion comes from using the same name for the language and the ecosystem, so renaming the language to something like "nix lang" could reduce confusion. Then, controlling the domain is simply a good idea, whatever we decide to do with it. And potentially, it could be a place that hosts the nix-lang manual (or redirect to it)

[fricklerhandwerk]

Part of the confusion comes from using the same name for the language and the ecosystem

This is true and we should address it with NixOS/nix.dev#275.

controlling the domain is simply a good idea, whatever we decide to do with it.

Sure, it just does not help with the issue here.

[davidak]

i think it would be best to have nix.org for the package manager + resources about nixpkgs and nix lang and nixos.org for the linux distribution + deployment tools for it, like nixops

that would solve confusion like reported in NixOS/nixos-homepage#832

[fricklerhandwerk]

another argument for having a Nix-package-manager-specific web site is to manage the web rendering of Nix manuals in the Nix repo. Right now the path-level redirects are on nixos-homepage while the anchor-level redirects are on nix. redirects are important to keep existing links alive.

Here are two pull requests that should be in sync, but produce a tail of follow-up work that is highly likely to be missed unless someone remembers to update the redirects on nixos.org once the current master branch reaches a release:

• manual: remove "Writing Nix Expressions" chapter nix#6863
• add redirects to accommodate changes in Nix manual nixos-homepage#881

Having the Nix web site in the source repo would allow managing redirects without additional effort.

[Ericson2314]

Yeah I want to second that having "NixOS" be the umbrella term for the whole ecosystem is confusing and we should move away from doing that.

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/usability-study-session-2/21400/1

[fricklerhandwerk]

We could even consider renaming the GitHub organization to Nix to match the hopefully-soon-to-be authoritative terminology and better support the (technically and morally correct) narrative that Nix is at the core of the Nix ecosystem. I'd even go as far as proposing to rename the NixOS Foundation to Nix Foundation.

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/landing-page-is-completely-unclear-for-new-users/22990/3

[zimbatm]

Somebody already registered nixlang.org and nix-lang.org.

I'm holding nixlang.com for the community

[bryanhonof]

I recently bought the getnix.org domain. I intend to make this a place to define a few streams, like https://getfedora.org/ does. So, there'd be a little box that explains and links to relevant resources for Nix as a package manager, another one for NixPkgs, one for NixOS, and so forth.

Furthermore, I'm open to transferring this to the NixOS foundation if they ever desire the domain.

[gilice]

I noticed nix.guide is currently free.
Maybe we can arrange to move nix.dev over to nix.guide and make nix.dev the main domain

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2023-04-11-documentation-team-meeting-notes-40/27261/1

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2023-10-23-documentation-team-meeting-notes-88/34562/1

[infinisil]

Moving this to the org repo, as this is about project and technical direction, which doesn't fall under the foundation's purview, but rather the SC's.