| 22 Oct 2022 |
|  brainrake joined the room. | 11:11:21 |
| brainrake | ๐ | 11:12:11 |
 ruby | Hi all - popping in to say I'd love to help lend a hand with contributing to Nix documentation! Was watching Valentin's talk on the NixCon livestream last night, and it's nice to see that we've got a strong effort growing to help address one of my biggest pain points with using Nix, as well as recommending it to my friends. More than happy to lend a hand whereever needed ๐ | 11:44:03 |
| brainrake | We're having a meeting about that right now ^ | 12:02:45 |
 Yuki (they/them) | We're currently having a meeting at NixCon. You can lurk what we're thinking/talking about: https://pad.lassul.us/gshjat31S9uSDX5GwhKeOw?edit | 12:00:58 |
| brainrake | This is a service that sends you random issues to review in configurable intervals
https://www.codetriage.com/ | 12:03:14 |
| Yuki (they/them) | In reply to @yuki:backalley.club
We're currently having a meeting at NixCon. You can lurk what we're thinking/talking about: https://pad.lassul.us/gshjat31S9uSDX5GwhKeOw?edit Essentially, we're discussing on bootstrapping the documentation contribution pipeline | 12:01:53 |
| ruby | In reply to @brainrape:ggpeti.com
This is a service that sends you random issues to review in configurable intervals
https://www.codetriage.com/ oh this is cool! might give it a go | 12:08:20 |
|  pkharvey joined the room. | 14:31:39 |
|  alejandrosame joined the room. | 15:29:22 |
|  Tobbe joined the room. | 16:56:17 |
 waldyrious | In reply to @waldyrious:matrix.org
Oh, it looks like a room can belong to both a space and one of its subspaces (e.g. the NixOS on ARM room does this). Could the same be done for this room? grahamc (he/him) / Domen Koลพar โ do you think this could be done for this room? I.e. make it be included in both the "teams" subspace and the top-level NixOS space? | 20:03:22 |
| Yuki (they/them) | I wonder whether the documentation for everything related to contributing documentation should have a dedicated section in nix.dev | 21:45:08 |
| Yuki (they/them) | Meh, Iโll just do it next week and make a PR so yโall can see instead of wasting time explaining it here. | 21:47:08 |
| 24 Oct 2022 |
|  Alex joined the room. | 21:10:38 |
| Alex | The "Nix language basics" link under the "Next steps" section of https://nixos.org/guides/ad-hoc-developer-environments.html is broken.
It seems like it was meant to link to https://nix.dev/tutorials/nix-language#reading-nix-language, but that page hasn't been put on nixos.org. | 21:12:47 |
| 25 Oct 2022 |
 olaf | In reply to @alex:tunstall.xyz
The "Nix language basics" link under the "Next steps" section of https://nixos.org/guides/ad-hoc-developer-environments.html is broken.
It seems like it was meant to link to https://nix.dev/tutorials/nix-language#reading-nix-language, but that page hasn't been put on nixos.org. the issue should be in this script: https://github.com/NixOS/nixos-homepage/blob/master/scripts/copy-nix-dev-tutorials.sh either open a issue in the repository (or create a pr if you have the time). | 06:37:11 |
|  nikstur joined the room. | 21:53:10 |
| 26 Oct 2022 |
|  fsbof joined the room. | 00:10:35 |
 fricklerhandwerk | Alex: made a pull request to fix that: https://github.com/NixOS/nixos-homepage/pull/929 | 09:42:18 |
 chreekat | Some feedback from having someone ask me about flakes: after viewing https://nixos.wiki/wiki/Flakes ("clear as mud") and after I linked them to https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html#description, they still say "It still doesn't say what they actually do... or why they are called flakes" | 10:42:15 |
| chreekat | they comment that flakes seem to be described in terms of other Nix features, "and thus impenetrable" | 10:42:50 |
| chreekat | In my own opinion, it's not about what flakes "do", but what Nix can do with them. Maybe the docs could highlight that | 10:44:05 |
 Sandro ๐ง | well, it is about what flakes can do because nix just imports some source code that flakes downloaded and turns on some tighter isolation (--pure). | 14:24:53 |
| Sandro ๐ง |
Flakes replace nix-channel completely in a reproducible and manageable way, so that every project and system can use their own flake.
| 14:26:02 |
 joepie91 ๐ณ๏ธโ๐ | chreekat: first pass at a better 'headline' description:
Flakes are a new feature of Nix, that makes it easier to combine package[?] definitions from different sources. It also allows maintainers of different sources to depend on each other, without breaking the guarantees of Nix, and without requiring you as the user to configure those dependencies manually.
thoughts?
| 14:48:01 |
| chreekat | In reply to @joepie91:pixie.town
chreekat: first pass at a better 'headline' description:
Flakes are a new feature of Nix, that makes it easier to combine package[?] definitions from different sources. It also allows maintainers of different sources to depend on each other, without breaking the guarantees of Nix, and without requiring you as the user to configure those dependencies manually.
thoughts?
I think it's getting there! Some suggestions:
- Suggestion: "Flakes make it easier to ..."; make it timeless
- Concern: "combine package definitions from different sources". Would it be clearer to say "make it easier to specify your package's dependencies"?
- Concern: Who is the audience, anyway: the package author, or the package user? I know the new
nix has a bunch of bells and whistles for the user, but are those because of the better dependency handling or something else?
- Suggestion: be specific about "guarantees of Nix"
| 14:58:10 |
| chreekat | Even "Flakes make it easier to..." implies the thing that came before, though. :) Newcomers won't know the difference | 15:00:23 |
| chreekat | "Flakes are a mechanism for ..." | 15:00:39 |
| chreekat | Although I do think it's useful to have a comparison to the old way | 15:00:59 |
