| 15 Mar 2024 |
 Eli Flanagan | I'll try git-send-mail patch approach per https://discourse.nixos.org/t/about-the-patches-category/477. | 17:31:37 |
 danielsidhion | In reply to @efx:matrix.org
I just created a GitHub account and seem to be unable to fork NixOS/nixpkgs. I'll work on the patch separately and may need some assistance getting the bytes into NixOS/nixpkgs. What URL are you using to try to fork? What error are you getting? | 17:53:05 |
| Eli Flanagan | Using GItHub web UI from Linux. Tried Firefox and Brave. GitHub's web UI displays correctly but simply redirects to NixOS/nixpkgs | 17:53:51 |
| Eli Flanagan | i'm going to try to manually import a recent clone of nixpkgs and push to my profile | 17:54:12 |
| Eli Flanagan | It looks like I can start an "import" https://github.com/NixOS/nixpkgs into my private profile as a new repository.
Though I'm curious if some kind of locking behavior is at play upstream. | 17:57:07 |
| danielsidhion | Oh sorry I misinterpreted what you said. Can you try forking with the github cli? gh repo fork NixOS/nixpkgs | 17:58:39 |
| Eli Flanagan | huh, looks like something is up: failed to fork: HTTP 403: You cannot fork this repository at this time (https://api.github.com/repos/NixOS/nixpkgs/forks) | 18:06:16 |
| Eli Flanagan | I also cannot fork someone's fork. I'm betting this is specific to the unique fact I just created this GitHub account. Thus, I'll wait till next week to try. | 18:13:36 |
| danielsidhion | That could be it. Could also try contacting their support to see what's going on, I couldn't find anything on their website about new account limitations | 18:15:18 |
| Eli Flanagan | honestly have wandered too far down this rabbit hole. This is a patch for my PR whenever I can: https://gist.github.com/eli0f/f461a00a6746609b6bcf07eee68091f1 | 18:16:11 |
| danielsidhion | That link gives me a 404 page | 18:16:55 |
| Eli Flanagan | eek, i'm using my SourceHut account. I marked the Gist as public but looks like I don't exist yet :) | 18:19:08 |
| Eli Flanagan | https://paste.sr.ht/~efx/7ff9532c1b8509e3482e990e5a07813cba7ee487 | 18:20:33 |
 infinisil | We welcome Johannes Kirschbauer @hsjobeki, author of the accepted RFC 145 and https://noogle.dev/, to the docs team! 🚀 | 19:42:34 |
| infinisil | Homepage PR: https://github.com/NixOS/nixos-homepage/pull/1350 | 19:42:58 |
|  @grahamc:nixos.org joined the room. | 21:48:35 |
| infinisil | ryantm: Would be great if you could synchronise with the docs team a bit more regarding https://github.com/NixOS/nixpkgs/pull/108063, it looks like you want to merge it soon :) | 23:28:14 |
| 16 Mar 2024 |
|  kait joined the room. | 03:35:37 |
| kait | hello, it would be better if the link to this room was a generic matrix.to instead of via the element app | 03:38:35 |
| kait | (on this page https://nixos.org/community/teams/documentation/ ) | 03:38:45 |
| kait | e.g. https://matrix.to/#/#docs:nixos.org | 03:39:08 |
| kait | https://matrix.to/#/#docs:nixos.org | 03:39:17 |
| danielsidhion | I think so | 03:41:27 |
| infinisil | kait/: Agreed! Could you PR this? Source is https://github.com/NixOS/nixos-homepage/blob/main/src/content/teams/11_documentation.mdx | 03:42:14 |
| kait | sure! thanks for the link :) | 03:43:16 |
 ryantm | In reply to @infinisil:matrix.org
ryantm: Would be great if you could synchronise with the docs team a bit more regarding https://github.com/NixOS/nixpkgs/pull/108063, it looks like you want to merge it soon :) Mainly I'm trying to get it merged so others can easily try it out and try to do it in the most self contained way so it is low risk and can be ripped out easily. | 03:49:14 |
| infinisil | ryantm: I guess especially @pennae, who has been saying a lot that nixos-render-docs can already render with multiple pages with some small changes to the code. Furthermore Johannes Kirschbauer @hsjobeki and danielsidhion who have been investigating existing docs rendering tools to see if we could maybe not roll our own tooling at all. Your PR introduces yet another custom-built tool 😅 | 03:53:55 |
| infinisil | I think we need a bit more convergence in docs tooling, so decreasing the different tools. We can still introduce new tools, but then we should also eventually deprecate another. I guess that's what your intending with your mmdoc, to replace nixos-render-docs | 03:55:53 |
| infinisil | That could be fine, but then we need to make sure that mmdoc supports everything that nixos-render-docs does and that somebody can maintain it. While nixos-render-docs is also pretty much maintained by just @pennae, it's written in Python, which at least from a superficial look is a lot more accessible than a C code base like your mmdoc 😅 | 03:58:25 |
| danielsidhion | To add a bit to this - looks like one of the motivations is to introduce a fast docs building tool because the nixos html manual and manpages get built for nixos (depending on the nixos config). I haven't yet dug into why we need to build the html manual for the nixos config at all, but in any case, Johannes Kirschbauer @hsjobeki and I are looking to converge on less tooling mostly for the html part, and focused on the usual web docs experience, not the in-your-os docs experience. | 04:06:42 |
