Nix Documentation | 381 Members | |
| This is the official channel for documentation in the Nix ecosystem. The documentation team meets here. More information: https://nixos.org/community/teams/documentation Video conference: https://jitsi.lassul.us/nix-documentation Meeting notes scratch pad: https://pad.lassul.us/p-Y8MjU2SdSD5qO1fnpCPA Past meeting notes: https://discourse.nixos.org/search?q=documentation%20team%20meeting%20order%3Alatest | 71 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Sep 2024 | ||
| I found wiki to be easier to contribute to definitely | 21:21:24 | |
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 | |
| 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 | |
| this doesn't need an rfc does it? | 21:28:50 | |
| 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 | |
| * 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 | |
| * 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 | |
| * 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 | |
| * 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 | |
| * 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 | |
| repology statistics could be useful too | 21:41:21 | |
going to bed, I'll see about the linkchecks via testers.lycheeLinkCheck across all these repos tomorrow | 21:42:44 | |
| 24 Sep 2024 | ||
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 | |
In reply to @infinisil:matrix.orghas anything been done for rendering docs in multiple pages since this discussion? | 07:51:46 | |
| would be cool if the epub build were fixed too | 07:52:38 | |
| @johannes.kirschbauer:scs.ems.host is there a noogle matrix channel? | 08:00:49 | |
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 | |
In reply to @phanirithvij:matrix.orgNo. But you can ask questions here as well i guess | 08:02:29 | |
| in the readme it is mentioned pagefind is only available in the production build | 08:03:07 | |
| danielsidhion: Is also kind of afk since ~springtime havent heard anything from him | 08:03:24 | |
| if I wish to self host noogle locally do I need pagefind | 08:03:26 | |
| Pagefind is the search engine, so yes, if you want the search. | 08:04:25 | |
"Production build" means npm run build | 08:04:57 | |
| Its a completely static page, you can selfhost it. | 08:05:15 | |
| ok I'll try it out | 08:05:48 | |
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 | |
| 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 | |
| Just asking if i this would hit some right spot. | 09:30:42 | |
In reply to@phanirithvij:matrix.orgHi, 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 | |
| 12:34:49 | ||