[joooscha]

One big issue with the NixOS wiki is that the maintainer of the web server is unresponsive for a long time [0]. Therefore, the wiki software is really out of date and using the page editor is a real pain in the butt [1].

I tried to write more for the wiki while learning things about NixOS. But it's so annoying to make changes that I eventually gave up.

I really like NixOS and Nix in general, it just lacks a central and organized, community maintained documentation like the Arch wiki. So, I hope either the maintainer will eventually become available again (unlikely IMO) and update the server, or we could mirror the current wiki on a new server.

[0] - https://github.com/nix-community/wiki/issues/46

[1] - https://github.com/nix-community/wiki/issues/40

[winny314]

I share your concerns. I've been chatting with a few people about this and made various false starts... It might not be my project, but I felt I could write down the risks I saw in how the wiki is ran: https://nixos.wiki/wiki/User:Winny/WikiRisks (including vulnerable server software)

[joooscha]

The next big problem with NixOS documentation is that there are a lot of smaller tutorials scattered around the web. Every page with a different style, focus, and depth.

What we need is one central wiki, where any problem search can begin. This is what makes the Arch wiki so great.

[freeere]

And why don't you setup a new server yourself but instead just complain and wait?

Also your cves if they are real why not showing how to exploit them?

[Mic92]

Because forking is also expensive and people would need to discover the new domain. Otherwise I would already have done it. We already have the issue of having too many different sources of documentation. And hacking the wiki is the last thing I want to do... I don't want get visits from the police from $someone.

[winny314]

Agreed. We want the wiki to listen to the community's needs and ensure continuity of it. This means a team is likely needed.