| 19 Oct 2022 |
 waldyrious | Oh, thanks for the explanation, Linux Hackerman. I hope that experience improves in the future :) | 08:54:28 |
 raboof | In reply to @linus:schreibt.jetzt
it's a weird behaviour, you have to join the subspaces to see the rooms I think TIL subspaces are even a thing - and indeed super confusing that a room you joined that is in a subspace only starts showing up in its 'superspace' after you joined the subspace itself as well. | 08:54:33 |
| waldyrious | Do subspaces show up at the same level as top-level spaces in the UI? I wouldn't want to pollute my list of spaces just for one channel | 08:55:52 |
| waldyrious | Oh, it looks like a room can belong to both a space and one of its subspaces (e.g. the Nix on ARM room does this). Could the same be done for this room? | 08:57:19 |
| waldyrious | * 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? | 08:57:33 |
 Linux Hackerman | otherwise there's the discourse forum at https://discourse.nixos.org/ | 09:10:39 |
| Linux Hackerman | Yeah I think Matrix is the biggest for real-time chat | 09:10:39 |
| Linux Hackerman | In reply to @waldyrious:matrix.org
Do subspaces show up at the same level as top-level spaces in the UI? I wouldn't want to pollute my list of spaces just for one channel no, they don't | 09:40:15 |
| 20 Oct 2022 |
|  hjulle joined the room. | 12:04:34 |
|  Jool joined the room. | 14:32:01 |
| 21 Oct 2022 |
 aktaboot | https://github.com/humancalico/nix-learning | 06:14:39 |
|  i97henka joined the room. | 09:22:41 |
|  adamcstephens joined the room. | 17:12:30 |
|  Yuki (they/them) joined the room. | 21:28:00 |
| 22 Oct 2022 |
|  ruby joined the room. | 04:52:26 |
 fricklerhandwerk | Planning what to do in the next 3 months: https://pad.lassul.us/gshjat31S9uSDX5GwhKeOw?edit | 08:14:49 |
|  Minijackson joined the room. | 08:29:43 |
|  john-rodewald joined the room. | 10:05:22 |
| john-rodewald set a profile picture. | 10:08:49 |
 FRidh | I think we should work to having testable examples. That is, CI test the code in tests. Of course our integration tests do that exactly for certain guides. But otherwise, I think we may learn here fromother ecosystems | 10:37:03 |
| FRidh | For discoverability we can tag hooks. https://github.com/NixOS/nixpkgs/issues/197070 This way we can find them easier and include in docs or highlight them on the packages website | 10:40:27 |
|  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 |
