| 6 Jul 2023 |
 pennae | there's no benefit to adding that much complexity over a small script that's pretty much inotifywait | while read; do nix-build; done | 15:22:09 |
| pennae | (we're in favor of the script fwiw) | 15:22:30 |
| pennae | we really have to get other things in order first before live-reload even begins to make sense | 15:33:50 |
 ronef | Quick update & question. We plan to announce the migration of Nix.dev to the community/foundation.
- Let me know if there's any thoughts on that
- I thought to take advantage of that announcement and potentially mention that folks can join the documentation team if they wish to contribute. Would this be relevant/interesting? If so, what's the best way for an interested community member to reach out?
| 15:44:05 |
 @zmitchell:matrix.org | In reply to @ronef:matrix.org
Quick update & question. We plan to announce the migration of Nix.dev to the community/foundation.
- Let me know if there's any thoughts on that
- I thought to take advantage of that announcement and potentially mention that folks can join the documentation team if they wish to contribute. Would this be relevant/interesting? If so, what's the best way for an interested community member to reach out?
- I think it's good to make the announcement with the context that it's intended to be the home of Nix documentation, but there's lots of work to do in order to get it looking how we want.
- I think the best place would be to direct them to this page (https://github.com/NixOS/nix.dev/tree/master/maintainers) since it has links to our weekly meetings, how people can contribute, etc. We can always use more maintainers. The best way to get in touch is through our weekly meetings since it's more efficient to transmit context that way. If they can't make the meetings, which is totally understandable, I would say the Nix Documentation Matrix channel (this channel).
| 16:22:05 |
| ronef | Sending the announcement for review, feel free to edit directly :) | 16:55:17 |
| @zmitchell:matrix.org | I think we should add a linkchecker run triggered on a timer to nix.dev GitHub Actions. I pretty frequently get failed CI runs that have nothing to do with my changes because an anchor link somewhere broke. For instance: here | 18:34:51 |
| 7 Jul 2023 |
|  tnias left the room. | 20:24:41 |
| 9 Jul 2023 |
|  kookie changed their display name from kookie to kookie (offline). | 14:31:49 |
| 10 Jul 2023 |
|  David A. Buser (boozedog) joined the room. | 15:47:52 |
| 11 Jul 2023 |
|  @quark97:matrix.org joined the room. | 03:39:32 |
|  thezaedus joined the room. | 03:42:59 |
| thezaedus | Hello all! | 03:44:35 |
 Pol | I already have such a thing based on prettier, works very well. | 06:00:47 |
| Pol | https://github.com/loophp/collection/blob/master/.github/workflows/prettier.yml | 06:01:21 |
| Pol | Here it is | 06:01:25 |
| ronef | Made the post on nix.dev -> https://discourse.nixos.org/t/nix-dev-moved-to-the-foundation-nix-official-documentation-site/30326
Let me know if I can change/edit anything | 21:49:49 |
| 12 Jul 2023 |
 infinisil | I have started documenting the overall file structure of Nixpkgs here and since I have a good overview of Nixpkgs, I'm considering taking ownership of at least the general Nixpkgs manual structure | 23:08:01 |
| 13 Jul 2023 |
|  vcunat changed their display name from @vcunat to vcunat. | 08:27:44 |
|  zuckerberg changed their profile picture. | 22:02:48 |
| 16 Jul 2023 |
|  @windchimesofmagic:matrix.org joined the room. | 02:36:59 |
| 17 Jul 2023 |
 Domen Kožar | 
Download 2023-07-17-120337_917x440_escrotum.png | 11:03:44 |
| Domen Kožar | 
Download 2023-07-17-120427_830x571_escrotum.png | 11:04:36 |
| Domen Kožar | quite consistent results over different social media | 11:05:03 |
 toonn | Is that really debatable at this point? It *should* teach about them. It should just also explain that they're still an experimental feature. | 12:46:44 |
| Domen Kožar | I've seen that the team decided not to touch flakes and I think that's the wrong direction, given what people are using these days. | 14:39:20 |
 asymmetric | It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using them, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for having a clearly defined line between what's supported and what isn't | 14:45:41 |
| asymmetric | * It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using flakes, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for having a clearly defined line between what's supported and what isn't | 14:47:43 |
| asymmetric | * It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using flakes, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for using stability as the demarcating line between what goes into nix.dev and what doesn't | 14:48:32 |
| Domen Kožar | We could make it a sprint topic for nixcon :) | 14:53:00 |
