23 Sep 2024 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial toy repo?
- also nixos-landscape has been offline for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
| 21:37:33 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial toy repo?
- also nixos-landscape has been unreachable for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
| 21:38:56 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial toy repo?
- also nixos-landscape has been inaccesible for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
| 21:39:06 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial personal repo?
- also nixos-landscape has been inaccesible for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
| 21:39:29 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial personal repo?
- also nixos-landscape has been inaccesible for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long time inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
| 21:40:04 |
loudgolem | repology statistics could be useful too | 21:41:21 |
loudgolem | going to bed, I'll see about the linkchecks via testers.lycheeLinkCheck across all these repos tomorrow | 21:42:44 |
24 Sep 2024 |
fricklerhandwerk | In reply to @phanirithvij:matrix.org
I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17 mindmaps, landscape, map-of-github, awesome-lists etc.
- are the graphviz graphs in that thread maintained anywhere? say in some unofficial personal repo?
- also nixos-landscape has been inaccesible for quite a while, that's a bummer
Another thing I'm interested in is to visualize/map nixpkgs health, i.e. how many packages are fresh, maintainer activity, most maintainted packages, packages without maintainers, long time inactive maintainers etc. all of these clearly visible somewhere like nixpkgs.health. I see rfc 180 which adresses a few of these.
For data wrangling, you may be interested in https://github.com/Nix-Security-WG/nix-security-tracker
There's a full DB model of Nixpkgs metadata and a worker for periodic evaluations. (The end game of this would be Hydra dumping all the information directly into the database for everyone to build tools around.)
| 00:34:33 |
loudgolem | In reply to @infinisil:matrix.org 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 😅 has anything been done for rendering docs in multiple pages since this discussion? | 07:51:46 |
loudgolem | would be cool if the epub build were fixed too | 07:52:38 |
loudgolem | @johannes.kirschbauer:scs.ems.host is there a noogle matrix channel? | 08:00:49 |
Johannes Kirschbauer @hsjobeki | In reply to @phanirithvij:matrix.org has anything been done for rendering docs in multiple pages since this discussion? As far as i am aware no. Pennae seems to do lix now. nixos-render-docs is now kind of unmaintained? Multipage rendering can be done, and it should be a straight forward task. Here are the steps that i have in my head rn.
-
build a table of track references (currently anchors)
-
split the manual during rendering into mutliple output pages (and where each reference is located)
-
make sure the references point to the correct subpage in output
-
write a client side redirect script for people having the old references
| 08:01:29 |
Johannes Kirschbauer @hsjobeki | In reply to @phanirithvij:matrix.org @johannes.kirschbauer:scs.ems.host is there a noogle matrix channel? No. But you can ask questions here as well i guess | 08:02:29 |
loudgolem | in the readme it is mentioned pagefind is only available in the production build | 08:03:07 |
Johannes Kirschbauer @hsjobeki | danielsidhion: Is also kind of afk since ~springtime havent heard anything from him | 08:03:24 |
loudgolem | if I wish to self host noogle locally do I need pagefind | 08:03:26 |
Johannes Kirschbauer @hsjobeki | Pagefind is the search engine, so yes, if you want the search. | 08:04:25 |
Johannes Kirschbauer @hsjobeki | "Production build" means npm run build | 08:04:57 |
Johannes Kirschbauer @hsjobeki | Its a completely static page, you can selfhost it. | 08:05:15 |
loudgolem | ok I'll try it out | 08:05:48 |
fricklerhandwerk | In reply to @johannes.kirschbauer:scs.ems.host
As far as i am aware no. Pennae seems to do lix now. nixos-render-docs is now kind of unmaintained? Multipage rendering can be done, and it should be a straight forward task. Here are the steps that i have in my head rn.
-
build a table of track references (currently anchors)
-
split the manual during rendering into mutliple output pages (and where each reference is located)
-
make sure the references point to the correct subpage in output
-
write a client side redirect script for people having the old references
getpsyched is currently working exactly on this under my supervision. It will take a while to get there, the devil is in the details. | 09:15:49 |
Johannes Kirschbauer @hsjobeki | fricklerhandwerk: Another thing that i'd like to get rid of are these include blocks in the nixpkgs/nixos docs. Because the overall structure can only be perceived from a recursive parser but not from a human. Which makes structural maintance/changes hard to understand. | 09:29:38 |
Johannes Kirschbauer @hsjobeki | Just asking if i this would hit some right spot. | 09:30:42 |
getpsyched | In reply to@phanirithvij:matrix.org has anything been done for rendering docs in multiple pages since this discussion? Hi, I've been working on the render docs as part of splitting the manuals into multiple pages. Currently the work is on getting a robust redirect system set up. As @Johannes Kirschbauer @hsjobeki outlined, I'm working on the same things and have pieced out the details in a roadmap which I'll convert into a formal documentation page after we hit the redirects milestone.
Feel free to track the progress through this diff: https://github.com/NixOS/nixpkgs/compare/nixos-24.05...GetPsyched:nixpkgs:render-docs
The base branch is set to 24.05 as we're aiming to backport these changes there and jump to master/24.11 and run our script again to retro-actively catch breakages. | 11:42:18 |
| @terru:raccoon.college left the room. | 12:34:49 |
| mei 🌒& changed their profile picture. | 23:25:17 |
26 Sep 2024 |
| Fabián Heredia set a profile picture. | 01:15:49 |
27 Sep 2024 |
| @zardian:matrix.org left the room. | 14:03:08 |
| loudgolem changed their display name from phanirithvij to loudgolem. | 14:38:01 |
| loudgolem changed their profile picture. | 14:38:28 |