Nix Documentation | 406 Members | |
| Discussion about documentation improvements around the Nix ecosystem | 81 Servers |
| Sender | Message | Time |
|---|---|---|
| 7 Mar 2024 | ||
| I read through the GitHub links and found this open PR that tried to add an error message: https://github.com/NixOS/nix/pull/6628. Prior art we might consider rallying to address. I know not C++ | 19:29:38 | |
| Also, Determinate Systems had documentation in their readme that they've since removed. Their nix-installer appears to fix the issue (https://github.com/DeterminateSystems/nix-installer/pull/714) | 19:35:47 | |
| Google Season of Docs applications are now open: https://developers.google.com/season-of-docs/docs/timeline | 21:42:43 | |
In reply to @jade_:matrix.orgI wonder if we couldn't do something in nixpkgs that would be a ready-to-go sshd that's specific to ssh-ng 🤔 | 21:44:39 | |
In reply to @jade_:matrix.org* I wonder if we couldn't do something in nixpkgs that would be a ready-to-go As in, it doesn't depend on outside state, and is configured exclusively for use with being used as a Nix builder. | 21:45:40 | |
In reply to @philiptaron:matrix.orgthe actual more reasonable thing here is a ssh service/subsystem/whateveritis like sftp | 21:48:56 | |
In reply to @jade_:matrix.orgNow that's a flavor I haven't heard in forever. Does anyone else do that?! | 21:49:30 | |
| subsystem seems like the absolute cleanest way of doing this tbqh, but putting PATH stuff in a drop in for sshd_config somewhere would also work | 21:55:44 | |
In reply to @jade_:matrix.orgDo you see a way of doing a drop-in style config? sshd_config isn't making me see any. I agree after reading the docs on subsystem that a nix subsystem would be 🔥 | 22:12:49 | |
| at least archlinux has /etc/ssh/sshd_config.d | 22:14:48 | |
In reply to @jade_:matrix.org* Do you see a way of doing a drop-in style config? sshd_config isn't making me see any. I agree after reading the docs on subsystem that a nix or nix-daemon subsystem would be 🔥 | 22:14:50 | |
| but i am guessing it is a distro thing maybe? | 22:15:04 | |
| That would be super lame. | 22:15:14 | |
| Of course it is: https://manpages.debian.org/unstable/openssh-server/sshd_config.5.en.html
| 22:23:46 | |
| fixing bad distro decisions in the installer seems a bit questionable, because of peoples jank configuration management systems or suchlike | 22:36:32 | |
| yeah, running a completely separate sshd seems more kosher to me. | 23:00:30 | |
| 23:13:13 | ||
| i'm looking at a doc PR which has a 23.11 backport label. Is it common to backport doc fixups? | 23:14:07 | |
| 8 Mar 2024 | ||
| 02:33:33 | ||
| so re: https://discourse.nixos.org/t/2024-03-07-documentation-team-meeting-notes-112/40963
is this about presentation frameworks for rendered outputs, or for actual splitting? because actual splitting has been there from day one (html:into-file), which we feel is being forgotten on a weekly basis | 02:35:06 | |
| Ping danielsidhion Johannes Kirschbauer @hsjobeki ^ | 02:41:52 | |
| Haven't seen it often, but I guess there's no problem with it if it makes sense | 02:43:11 | |
| like, nrd exists for the express purpose of creating manuals at least as useful as docbook was, with xrefs from modules to options etc, and not create totally garbage manpage output like current nix does. the syntax extension are icing | 02:43:13 | |
| we've recently been told that epub support is something at least a few still want, the infra behind html:into-file was with the express purpose of easily allowing any level of detail of splitting so you can make epub happen very easily. (it's not wired up for that right now, but it's like five lines of patch to do) | 02:44:41 | |
| I understand the frustration you're experiencing, especially considering the significant effort you've invested into the project. However, Danielsidhion and I are currently exploring alternative options because we're trying to providing the best possible experience for our users. This sometimes entails re-thinking our current approach. Adopting an off-the-shelf rendering framework that offers customization options could significantly enhance user-friendliness while reducing complexity and maintenance work. Daniel has a list of needed features like page search, intuitive navigation, handling cross references, md plugins, live editing etc, ultimately improving the overall user experience. I think we might need an RFC if we really want to migrate anyways. This would also allow potential epub users to show up. | 07:52:41 | |
| * I understand the frustration you're experiencing, especially considering the significant effort you've invested into nrd. However, Danielsidhion and I are currently exploring alternative options because we're trying to providing the best possible experience for our users. This sometimes entails re-thinking our current approach. Adopting an off-the-shelf rendering framework that offers customization options could significantly enhance user-friendliness while reducing complexity and maintenance work. Daniel has a list of needed features like page search, intuitive navigation, handling cross references, md plugins, live editing etc, ultimately improving the overall user experience. I think we might need an RFC if we really want to migrate anyways. This would also allow potential epub users to show up. | 07:53:42 | |
| * I understand the frustration you're experiencing, especially considering the significant effort you've invested into nrd.
However, Danielsidhion and I are currently exploring alternative options because we're trying to providing the best possible experience for our users.
This sometimes entails re-thinking our current approach. Adopting an off-the-shelf rendering framework that offers customization options could significantly enhance user-friendliness while reducing complexity and maintenance work. Daniel has a list of needed features like page search, intuitive navigation, handling cross references, md plugins, live editing etc, ultimately improving the overall user experience.
I think we might need an RFC if we really want to migrate anyways. This would also allow potential epub users to show up. | 07:54:32 | |
| also don't forget that manpages exist. | 07:55:24 | |
| nix regressed horrifically on its manpages, if you do the same you will do so much more damage than live editing or flashier navigation can give you | 07:56:23 | |
| also consider that nixos-search exists and would do rather better with richer xref medatadata rather than stuff that mostly works in html-only-and-maybe-pdf formats? | 07:57:51 | |