Sender | Message | Time |
---|---|---|
23 Sep 2024 | ||
fricklerhandwerk | In reply to @phanirithvij:matrix.org* Eh, not that much. There are like 2-3 regular contributors who have touched all of them, but otherwise these are mostly disjoint groups as far as I can tell. I mean, it's complicated. Define "a lot". There's not that many people working on documentation overall. | 21:20:30 |
fricklerhandwerk | * Eh, not that much. There are like 2-3 regular contributors who have touched all of them, but otherwise these are mostly disjoint groups as far as I can tell. I may be wrong. I mean, it's complicated. Define "a lot". There's not that many people working on documentation overall. | 21:20:53 |
loudgolem | I found wiki to be easier to contribute to definitely | 21:21:24 |
fricklerhandwerk | In reply to @phanirithvij:matrix.orgThey all have very different update cycles, and running the checks in some other location from where the source is modified will just lead to people having to jump hoops. Had that with the Nix manual, please don't. | 21:21:56 |
loudgolem | ok so gha per repo then, tested on corresponding stable manuals and sites and each repo can adjust the run frequency per its release cycle | 21:25:43 |
loudgolem | this doesn't need an rfc does it? | 21:28:50 |
loudgolem | I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17
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:17 |
loudgolem | * I'm also interested in things like this https://discourse.nixos.org/t/nix-ecosystem-mind-map/28682/17
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
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
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
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
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 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.orghas 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 As far as i am aware no. Pennae seems to do lix now. nixos-render-docs is now kind of unmaintained?
| 08:01:29 |
Johannes Kirschbauer @hsjobeki | In reply to @phanirithvij:matrix.orgNo. 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.hostgetpsyched 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 |