| 3 Jan 2024 |
 Chris McDonough | ty! | 20:06:39 |
 @johannes.kirschbauer:scs.ems.host | I'll join the meeting as well. I could need some help with migration of the nixpkgs manual rendering. (nixos-render-docs)
There are a lot of questionmarks in my head when it comes to section ids.
I'd like to discuss the future of that tooling after rfc145 was merged. Who has the ownership about this? @pennae or fricklerhandwerk ?
| 20:52:25 |
| @johannes.kirschbauer:scs.ems.host | * I'll join the meeting as well. I could need some help with migration of the nixpkgs manual rendering. (nixos-render-docs)
There are a lot of questionmarks in my head
I'd like to discuss the future of that tooling after rfc145 was merged. Who has the ownership about this? @pennae or fricklerhandwerk ?
| 20:52:39 |
 fricklerhandwerk | In reply to @johannes.kirschbauer:scs.ems.host
I'll join the meeting as well. I could need some help with migration of the nixpkgs manual rendering. (nixos-render-docs)
There are a lot of questionmarks in my head
I'd like to discuss the future of that tooling after rfc145 was merged. Who has the ownership about this? @pennae or fricklerhandwerk ?
@pennae wrote all of it, I have only cursory knowledge of that code | 23:44:11 |
| fricklerhandwerk | Also I won’t be able to participate in meetings in the next two months or so | 23:44:53 |
| 4 Jan 2024 |
 infinisil | Johannes Kirschbauer @hsjobeki: I'll be there in the meeting, we could also take a look at the nixdoc PR | 01:39:44 |
 danielsidhion | infinisil: PR to document the conventions as discussed in the meeting: https://github.com/NixOS/nixpkgs/pull/278762
I've been adding this documentation-reviewers team on my PRs because it seems more appropriate than adding the documentation team. Is this appropriate, or should I just stick to adding the documentation team instead? | 20:05:59 |
| infinisil | danielsidhion: No that's perfect :) | 20:06:38 |
| danielsidhion | 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 | 20:34:17 |
| danielsidhion | Chris McDonough: check the message above. I'm also creating some more issues on the nixpkgs repo for things I find as I read the manual. Those are either for extra documentation, or things in nixpkgs itself. I'd rather not paste a bunch of links here, but you can check issues I opened in the nixpkgs repo (I'm @danielsidhion there too) | 20:36:24 |
| infinisil | danielsidhion: Very nice! | 21:05:55 |
