In reply to @danielsidhion:nixos.dev
Also as discussed in the meeting, here's a quick overview of what I'm doing: for no reason at all, I decided it would be a good idea to go through the Nixpkgs manual source and update all examples to the admonition syntax as specified in the doc readme. As I did this, I realised that other things could also be updated to follow a more consistent style, and I also started finding a lot of outdated content in the manual, which I'm making an effort to also update. More than one person has asked how they could help, so I created a tracking issue here: https://github.com/NixOS/nixpkgs/issues/278769

In reply to @asymmetric:matrix.dapp.org.uk
Regarding this issue, in the event the documentation team were to receive some funds, I wonder how prepared we would be, in terms of distributing funds, both to people and to tasks. fricklerhandwerk you probably have experience here? Is there some document that it would make sense to take a look at before this call?

I read the entire nix docs but I think it's the kind of documentation that's only useful if you already kind of get what's going on. It feels like you have to gather the knowledge from various random blogs. Last time I checked there surprisingly was not a single book which covers nix. I feel like a comprehensive book which teaches nix from the ground up and explains all the different ways of using nix would really help me and I would purchase such a book without hesitation if it existed.

still lots of work to do with the nix docs
https://news.ycombinator.com/item?id=38930947

And I don't mind reading 'code as docs' in general but it's pretty much required here.

this sentiment remains, even from people enthusiastic about nix...
https://news.ycombinator.com/item?id=38931306

In reply to @9999years:matrix.org

I read the entire nix docs but I think it's the kind of documentation that's only useful if you already kind of get what's going on. It feels like you have to gather the knowledge from various random blogs. Last time I checked there surprisingly was not a single book which covers nix. I feel like a comprehensive book which teaches nix from the ground up and explains all the different ways of using nix would really help me and I would purchase such a book without hesitation if it existed.

still lots of work to do with the nix docs
https://news.ycombinator.com/item?id=38930947

In reply to @mcdonc:matrix.org
"no"?

In reply to @mcdonc:matrix.org
speechless

It was a short, low content message, and it's not clear what the point of it was.

The simplest way to respond to it that wasn't "this is incorrect because....", is to disagree with a "no".

In reply to @mcdonc:matrix.org
you know, i submitted a pr a while back to the nixpkgs docs... and i attended a docs meeting in jitsi... and i volunteered to help.. but i'm starting to have second thoughts

In reply to @mcdonc:matrix.org
alrighty then

A little more carefully however, if I am understanding the subtext of your message properly:

• if my comment is what is making you "lay down a threat", then consider that I am not a member of the Nix documentation team. You should base such decisions off of your interactions with the team leader (fricklerhandwerk) and their deputies (e.g. infinisil)

• if you believe my message is "rude", you should consider whether or not the person I was responding to (who was not you, as far as I know), has bothered scrolling up to read some of the discussion in this channel.

But to be honest, it's very difficult to figure out your chain of comments.

In reply to @mcdonc:matrix.org
you know, i submitted a pr a while back to the nixpkgs docs... and i attended a docs meeting in jitsi... and i volunteered to help.. but i'm starting to have second thoughts