| 21 Jul 2021 |
 samueldr | garbas: reminder that in 19 minutes there's that bi-weekly call | 18:41:30 |
| samueldr | (or not?) | 19:01:03 |
| samueldr | (there is) | 19:18:27 |
| samueldr | (there was) | 20:18:14 |
 tomberek | samueldr: this is what I meant by a non-invasive way to try out Nix: https://github.com/nix-dot-dev/nix.dev/pull/169 | 20:33:42 |
| samueldr | nice! | 20:34:21 |
 matthewcroughan - nix.zone | Huh I didn't realise you could contribute to nix.dev. That is certainly cool. Though I believe sphinx/rst are the wrong format to use, I may set up an alternative that uses MkDocs. MkDocs lets you use templating (jinja) and python to change the page contents, from within the MD file so you can have smart pages that have logic in them. Like if page.metadata == arm64 then include ../common/arm64.md | 20:42:37 |
| samueldr | ugh, please, not yet another source of documentation, it's already too fragmented | 20:43:35 |
| matthewcroughan - nix.zone | I was looking for evidence of automation/coding in the official Nix docs, and it looks like it's 100% hand written? | 20:43:43 |
| samueldr | "official docs" is still un flux because of RFC#whatever the one for markdown | 20:44:08 |
| samueldr | * "official docs" is still in flux because of RFC#whatever the one for markdown | 20:44:15 |
| matthewcroughan - nix.zone | I just don't think a lot of the stuff that is handwritten can be maintained. | 20:44:19 |
| matthewcroughan - nix.zone | Well it can, with dedication! But it's harder than it has to be. | 20:46:05 |
 andi- | Isn't everything apart from API docs manual writing anyway? How can you automate that and nix.dev is mostly not api docs IIRC. | 20:46:59 |
| samueldr | (to circle back to the actual topic, rather than fresh bikeshedding) tomberek: thanks, this will help with my lack of knowledge with docker when actually writing docs for $PROJECT | 20:47:31 |
| matthewcroughan - nix.zone | Of course not all can be. I'm just suggesting that sphinx/rst make it practically impossible to automate. | 20:48:17 |
| matthewcroughan - nix.zone | * Of course not all can be. I'm just suggesting that sphinx/rst make it practically impossible to automate anything other than Python docs. | 20:48:30 |
| matthewcroughan - nix.zone | https://squidfunk.github.io/mkdocs-material/reference/variables/ | 20:49:16 |
| matthewcroughan - nix.zone | I will not discuss here any further since I realise I'm overtaking the topic. My bad. | 20:49:37 |
| samueldr | right, tomberek, "authoring format" is probably another reason I forgot about when discussing that earlier | 20:53:48 |
| tomberek | samueldr: I’d be happy to do an bit of Docker introduction with you | 23:37:57 |
| samueldr | I kind of don't want to ;) | 23:38:21 |
| samueldr | makes it easier to gauge whether things only make sense to a docker enthusiast or not :) | 23:38:40 |
| samueldr | though with that said it's more tongue-in-cheek, I'm sure it's worthwhile to better understand all of this and how where Nix helps | 23:39:47 |
| 22 Jul 2021 |
 ryantm | NixOS slightly mentioned on Linus Tech Tips :) https://youtu.be/_Ua-d9OeUOg?t=121 | 20:43:19 |
| matthewcroughan - nix.zone | Yeah that's unexpected | 20:49:35 |
| matthewcroughan - nix.zone | I think it marks a significant milestone, that we've come far enough to be on that radar. | 20:49:55 |
| 23 Jul 2021 |
 jonringer | "hardmode", compared to the other distros, I would agree. Lol | 01:22:14 |
 davidak | maybe we could get to intermetiate with an easy gui installer for desktop users. not sure if it ever could be beginner-friendly with all the options. maybe we would need a gui configuration editor that hides everything a desktop user does not need (with option to show everything). or a distro based on NixOS, like Manjaro | 01:25:19 |
| jonringer | I think the problem is that nixos is a "choose your own adventure" distro. Other distros have a much easier time as the provide one well polished experience. | 01:41:56 |
