 | Nix Documentation | 432 Members |
| Discussion about documentation improvements around the Nix ecosystem | 86 Servers |
| Nix Documentation | 432 Members |
| Discussion about documentation improvements around the Nix ecosystem | 86 Servers |
| Sender | Message | Time |
|---|---|---|
| 28 Apr 2023 | ||
 @wiseh:matrix.org | Hello! Quick question: do we have any official resources that talk about how to split Nix configuration files? I found this very detailed answer https://unix.stackexchange.com/questions/272660/how-to-split-etc-nixos-configuration-nix-into-separate-modules and would like to see if it's possible to merge it to the official documentation. Would there be any problems with licenses/permissions, by the way? | 01:53:29 |
 @drupol:matrix.org changed their profile picture. | 08:42:42 | |
 fricklerhandwerk | wiseh: there may be something about this on nixos.wiki. kookie is currently working on NixOS module documentation and probably has a better overview on existing resources. In terms of licensing, StackOverflow user contributions appear to be CC-BY-SA, so importing contents to nix.dev with appropriate attribution should be fine. | 08:50:15 |
 kookie | All official (and unofficial) resources I'm currently aware of are documented in my PR where I'm trying to consolidate the material into one comprehensive guide (which we may later split up again if it's too unwieldy): https://github.com/NixOS/nix.dev/pull/526/files#diff-e75e47b6a9b2aca045fecf736f0d852f93f38ffada53744155eca9991cfeb83fR3 | 08:56:39 |
| kookie | * All official (and unofficial) resources I'm currently aware of are documented in my PR where I'm trying to consolidate the material into one comprehensive guide (which we may later split up again if it's too unwieldy): https://github.com/NixOS/nix.dev/pull/526/files#diff-e75e47b6a9b2aca045fecf736f0d852f93f38ffada53744155eca9991cfeb83fR3 wiseh | 08:56:43 |
 asymmetric | In reply to @fricklerhandwerk:matrix.org I would find it a bit strange to find copy-pasted SO answers on nix.dev. I'm also wondering how it would affect SEO. Typycally, copy-pasting (espcially from SO) is detrimental to SEO, I believe? | 09:37:37 |
| fricklerhandwerk | In reply to @asymmetric:matrix.dapp.org.ukCopy-pasting should always and only be the first step to keep track of provenance. I surely wouldn't merge that answer verbatim. | 09:58:21 |
| fricklerhandwerk | In reply to @asymmetric:matrix.dapp.org.uk* Copy-pasting should always and only be the first step to keep track of provenance. I surely wouldn't merge that particular answer verbatim. But before even starting a PR, one should ask the question what kind of documentation that is, and where it should go. | 09:58:53 |
| fricklerhandwerk | Unfortunately we don't yet have a concept for managing recipes. Maybe we should put this on the agenda for the next team meeting, since those recipes keep piling up. | 09:59:20 |
| fricklerhandwerk | * Copy-pasting should always and only be the first step to keep track of provenance. I surely wouldn't merge that particular answer verbatim. But before even starting a PR, one should ask the question what kind of documentation that is, and where it should go. | 09:59:59 |
| fricklerhandwerk | We will have a preparatory video call for the 2023-05-27 Nix developer workshop in Zürich next Tuesday: https://discourse.nixos.org/t/community-calendar/18589/67 The purpose is to explore needs and interests, and then narrow down workshop topics for the three available slots in order to make best use of everyone's time once we're in a room together. This is mainly for people who want to participate in the workshop itself. Working on documentation is a particular area of interest, and the workshop would be a great opportunity to leverage the combined expertise of the group. | 10:50:25 |
| fricklerhandwerk | Please write me a direct message if you want a Google Calendar invite so it can show up in your reminders. | 10:50:53 |
| 1 May 2023 | ||
| @wiseh:matrix.org |
Thanks for the clarifications... It is certainly not very appropriate to copy and paste. The proposal was a bit crude, sorry for that 😅. But then... How could we integrate this kind of information in an official source? I mean, it is certainly not something vital, but I think it is part of a "peripheral" documentation that allows to approach the ideas of Nix through something as trivial as cleaning and tidying up a bit the configurations. In fact when I saw it it reminded me at some point of the Nix pills, because I could achieve a goal but on the way I learned/remembered a simple use of Nix expressions, the way to work with functions, attr-sets, etc. (Because of that I also thought it would fit more as a tutorial than as a recipe, am I wrong?) (I also don't rule out that maybe I overestimated the content, and was attracted by the very kind way of presenting it!) | 06:24:50 |
| fricklerhandwerk | wiseh: That particular piece could be a how-to guide. We’re still in search of a paradigm where to put those, how to handle the overall collection and how to integrate it with the rest of the docs. | 12:27:15 |
| fricklerhandwerk | I wanted to talk about this today, but unfortunately I can‘t make the meeting today due to urgent private matters. Hopefully we’ll find time on Thursday. | 12:28:42 |
| fricklerhandwerk | * I wanted to talk about this today, but unfortunately I can‘t make the meeting due to urgent private matters. Hopefully we’ll find time on Thursday. | 12:29:00 |
| kookie | I thought I'd make it to today's meeting but it's international workers day and I definitely won't work today 😅 Happy May day everyone 🥳 ✨ | 14:22:05 |
| 2 May 2023 | ||
 @manheraz:matrix.org joined the room. | 05:35:33 | |
| 3 May 2023 | ||
 infinisil | https://www.reddit.com/r/NixOS/comments/135j2y2/post_on_nixnixos_for_newcomers/jikj0nt/ | 02:45:41 |
| @manheraz:matrix.org left the room. | 05:17:48 | |
 @kranzes:matrix.org joined the room. | 19:23:13 | |
 @federicodschonborn:matrix.org joined the room. | 23:57:04 | |
| 4 May 2023 | ||
 @zmitchell:matrix.org | Learning journey working group meets in 45 minutes | 12:16:08 |
| fricklerhandwerk | Thanks again everyone for joining. We were a bit scattered today due to availability, but thanks to everyone's input we made good progress on how to deal with how-to guides in the foreseeable future. | 15:04:45 |
 @pennae:matrix.eno.space | oh, right, meeting 😖 | 15:05:14 |
| fricklerhandwerk | We'll write down a few things that have to be done to get going with curating guides in a more structured fashion based on today's discussion. And then we will probably need lots of help to sift through what's out there and bringing that up to date. | 15:06:22 |
 j-k | sorry I was only there briefly, getting back into the swing of things after some distracted weeks of work | 15:34:34 |