Okay, interesting, I've been to nix.dev before, but I didn't know it was official (due to the reasons you pointed out).

And also, if that's the place where something like "How to configure a printer" would belong, the title and the subtitle "An opinionated guide for developers getting things done using the Nix ecosystem." should probably also be changed, but I'm not quite sure to what? What exactly would it be, if it's neither the manual nor the wiki and what would it be called? "NixOS Guides"? What would a nixos.org subdomain be? guides.nixos.org?

In reply to @asymmetric:matrix.dapp.org.uk

fricklerhandwerk: do you know what's blocking us from making nix.dev look more official? Thinking of things like:

• copyright footer mentioning Domen Kožar
• style being different
• lack of link from nixos.org
• no mention of it being official in landing page

In reply to @asymmetric:matrix.dapp.org.uk

fricklerhandwerk: do you know what's blocking us from making nix.dev look more official? Thinking of things like:

• copyright footer mentioning Domen Kožar
• style being different
• lack of link from nixos.org
• no mention of it being official in landing page

In reply to @asymmetric:matrix.dapp.org.uk
so if there are blockers around copyright transfer of nix.dev, this could be a way to sidestep those entirely, and solve visiblity from homepage and pagerank issues as well

It's not exactly that simple. What we really need is a clearly distinct presentation for the different ecosystem components (Nix, Nixpkgs, NixOS, and possibly others), and one integrated user story.

Currently we have no maintainers for NixOS documentation, but ironically this is what most new users come from and end up confused. nixos.org contains very little technical information and is more of an organisational hub, at least judging from where the updates are happening. nix.dev is trying to do the integration.

More context: https://github.com/NixOS/nix.dev/issues/290

I think we do have a clear vision what needs to be done, but lack of resources and problems with coordination to actually do it.

In reply to @asymmetric:matrix.dapp.org.uk
so if there are blockers around copyright transfer of nix.dev, this could be a way to sidestep those entirely, and solve visiblity from homepage and pagerank issues as well

It's not exactly that simple. What we really need is a clearly distinct presentation for the different ecosystem components (Nix, Nixpkgs, NixOS, and possibly others), and one integrated user story.

Currently we have no maintainers for NixOS documentation, but ironically this is what most new users come from and end up confused with. nixos.org contains very little technical information and is more of an organisational hub, at least judging from where the updates are happening. nix.dev is trying to do the integration.

More context: https://github.com/NixOS/nix.dev/issues/290

I think we do have a clear vision what needs to be done, but lack of resources and problems with coordination to actually do it.

It's not exactly that simple. What we really need is a clearly distinct presentation for the different ecosystem components (Nix, Nixpkgs, NixOS, and possibly others), and one integrated user story.

Currently we have no maintainers for NixOS documentation, but ironically this is what most new users come for and end up confused with. nixos.org contains very little technical information and is more of an organisational hub, at least judging from where the updates are happening. nix.dev is trying to do the integration.

More context: https://github.com/NixOS/nix.dev/issues/290

I think we do have a clear vision what needs to be done, but lack of resources and problems with coordination to actually do it.

In reply to @fricklerhandwerk:matrix.org
We're waiting for the NixOS Foundation to receive ownership of copyright and the domain. Technical issues can be fixed quickly.

In reply to @eisfunke:eisfunke.com
And regarding my original question about "where to put 'how to set up printing' and other stuff that currently lives in the wiki" – I'm still a little confused, because looking over the current version of nix.dev something like that would look very much out of place there

In reply to @eisfunke:eisfunke.com
And regarding my original question about "where to put 'how to set up printing' and other stuff that currently lives in the wiki" – I'm still a little confused, because looking over the current version of nix.dev something like that would look very much out of place there

Where to migrate what:

    Nix interaction: nix manual

    Language-specific build instructions: nixpkgs manual

    Package, service, or hardware configuration: nixos manual

    Overviews, tutorials, guides, and best practices: nix.dev

https://nix.dev/contributing/documentation#wiki

In reply to @infinisil:matrix.org
Who's doing that, what's the status? This doesn't seem to have moved along at all within months

Domen Kožar and the foundation board have to do this. I know that Théophane has looked into it somewhat recently. But board members are extremely time-constrained and have lots of things on their plate.

ronef could you prioritise this? We’re running into this problem continuously, and it would unblock a lot of things we wanted to do for a long time now.

In reply to @domenkozar:matrix.org
transferred the domain yesterday and signed the copyright transfer about a month ago

Awesome! I didn’t even know. Did you publish it in the board meeting notes somewhere? Couldn’t find it.

asymmetric: Since that’s settled, please go ahead with the necessary updates.

I will bring these two old PRs up to date this week:

https://github.com/NixOS/nix.dev/pull/262

https://github.com/NixOS/nixos-homepage/pull/882

In reply to @infinisil:matrix.org
Though it was moved to the same time as the learning journey meeting on Thursday..