| 27 May 2023 |
 Jan Tojnar | rski: hi, why did you undo https://nixos.wiki/index.php?title=Overlays&diff=7472&oldid=6543, there is no rationale in the edit summary | 11:20:09 |
|  NixOS Moderation Botchanged room power levels. | 16:40:28 |
| 29 May 2023 |
 abathur | In reply to @kranzes:matrix.org
If you can fix it here https://github.com/NixOS/nixos-homepage, please do so. I'll merge it. https://github.com/NixOS/nixos-homepage/pull/1054 was opened when I passed along a query about this | 16:08:50 |
|  ners joined the room. | 20:53:57 |
| 31 May 2023 |
|  Alper Çelik joined the room. | 10:53:00 |
| 1 Jun 2023 |
|  ruby changed their profile picture. | 07:07:58 |
| ruby changed their profile picture. | 07:34:38 |
| 2 Jun 2023 |
|  @wiseh:matrix.org changed their display name from wiseh to Dioprz. | 04:50:58 |
|  mei 🌒& changed their display name from ckie (they/them; limited keyboard usage, voice preferred) to ckie (they/them). | 22:19:32 |
| 3 Jun 2023 |
|  rendakuenthusiast left the room. | 08:02:32 |
|  Yuki (they/them) changed their display name from Yuki (they/them) to Yuki (they/them) (Old). | 15:33:23 |
|  proofconstruction joined the room. | 22:26:14 |
| 4 Jun 2023 |
|  Yuki Langley (they/them) joined the room. | 10:15:34 |
|  @federicodschonborn:matrix.org changed their profile picture. | 17:40:05 |
| 5 Jun 2023 |
 asymmetric | infinisil: any idea why i got another couple of updated calendar event emails? | 14:39:58 |
| asymmetric | for the team meetings | 14:40:02 |
| asymmetric | it's not clear from the emails what has been updated | 14:40:13 |
| asymmetric | * infinisil: any idea why i got another pair of updated calendar event emails? | 14:42:01 |
| asymmetric | * infinisil: any idea why i got another pair of calendar emails about updated events? | 14:42:14 |
 fricklerhandwerk | proofconstruction: here's the overview of the Nix ecosystem workshop participants created recently | 15:11:36 |
| fricklerhandwerk | 
Download Nix Developer Workshop – Architecture Diagram.svg | 15:11:43 |
| proofconstruction | Thanks! | 15:14:26 |
| proofconstruction | Is there any similar diagram for how the documentation is structured? | 15:14:59 |
| proofconstruction | Or intended to be structured, maybe | 15:15:10 |
| proofconstruction | I have an action item to begin one, if not | 15:38:10 |
| fricklerhandwerk | There is no diagram. Essentially, every component has some sort of reference documentation somewhere. We’re working on setting up nix.dev to provide guidance on how to use the “official platform” tools, i.e. with the other Diataxis categories. The manuals are linked from the top level navigation. | 15:38:44 |
| fricklerhandwerk | We may want to provide visual representation of the ecosystem architecture early on, but each component’s internal architecture should be left to be presented on its own terms. But I don’t think it’s a priority. | 15:45:51 |
| 6 Jun 2023 |
|  @tek:tryp.io joined the room. | 10:37:31 |
 sterni | it occurs to me that neither the manual nor CONTRIBUTING.md mention a clear policy for what manual-related commit messages should look like. I think there's a convention to have path-like prefixes like nixos/doc or doc, but maybe we should codify that. | 10:40:47 |
| fricklerhandwerk | Sure, go ahead and make a proposal. I think it can be fairly lightweight. Git tracks files changed, labels get added accordingly, and usually all one needs to judge what's going on at a glance is some keyword in the change statement, such as "document X" or "mention Y in the manual" | 11:28:15 |
