| 21 Apr 2024 |
 teto | jonringer: might I enquire why the quote of my pending PR description ? Is the descriptio not good enough :'( ? | 22:27:40 |
| 22 Apr 2024 |
 @jacg:matrix.org | teto: In yesterday's meeting the release editors were asked to ensure that the name of the affected package or service appear at the beginning of each note, for easy visual parsing/filtering of items. Yours was simply given as an example of a note where the package name first appears further in the text of the note. | 07:02:39 |
 jonringer | Yea, that was all | 14:39:27 |
| jonringer | You PR was just the first PR with the has changelog label.
Appreciate what you do for lua and vim :)
| 17:30:54 |
| jonringer | When referencing packages in release notes, example: https://github.com/NixOS/nixpkgs/pull/305965/files#r1575114124. I feel like we should:
- Keep upstream capitalization when referring to the project/brand (e.g. macOS, NixOS)
- Use the attr/installable path with codeblock when referencing the nixpkgs path (e.g.
pkgs.vim or just vim)
Not sure how people feel about my suggestion here. This fixates more on the nixos option rather than project itself.
| 17:37:52 |
| jonringer | I guess related to what I said above, is that trying to normalize related changes become odd when switching between referencing packages by their title vs their nixpkgs attr path:
postgresqlnow defaults to ...
MySQL now defaults ....
Should we trying to keep as nixpkgs as possible, unless it detracts from comprehension?
| 17:43:04 |
| jonringer | * I guess related to what I said above; is that trying to normalize related changes becomes odd when switching between referencing packages by their title vs their nixpkgs attr path:
postgresqlnow defaults to ...
MySQL now defaults ....
Should we trying to keep as nixpkgs as possible, unless it detracts from comprehension?
| 17:43:45 |
| jonringer | * I guess related to what I said above; is that trying to normalize related changes becomes odd when switching between referencing packages by their title vs their nixpkgs attr path:
postgresqlnow defaults to ...
MySQL now defaults ....
Should we try to keep diction "as nixpkgs" as possible? unless it detracts from comprehension?
| 17:45:22 |
| @jacg:matrix.org | I'm tempted to go for attribute names over brands, favouring comprehension over aesthetics. | 20:29:11 |
| 23 Apr 2024 |
| @jacg:matrix.org | Some notes give version numbers as code blocks, some as normal text. Should we make these consistent? If so, which way? I lean towards code blocks, to make them stand out. | 08:44:31 |
|  @theophane:hufschmitt.net joined the room. | 12:14:39 |
 Weijia | I'd prefer version numbers to be normal text, like 24.05 instead of 24.05. | 13:48:02 |
| jonringer | Do you have an example? | 15:06:50 |
| jonringer | In reply to @jonringer:matrix.org
Do you have an example? nevermind, took a look at https://github.com/NixOS/nixpkgs/pull/306235 | 15:22:07 |
| jonringer | I might side with Weijia on this one, the codeblocks are used extensively for packages and nixos options (things that are supplied by nixpkgs and NixOS). I don't think using codeblocks for versions would increase readability. | 15:24:19 |
|  @me:indeednotjames.com left the room. | 16:47:36 |
|  trofi left the room. | 21:13:26 |
| 24 Apr 2024 |
|  @stablejoy:matrix.org changed their profile picture. | 08:59:14 |
|  fpletz joined the room. | 09:29:06 |
| 25 Apr 2024 |
|  NixOS Moderation Bot banned jonringer (Banned until 2024/06/10 after deliberation of the Moderation team). | 21:12:05 |
| 26 Apr 2024 |
 Vladimír Čunát | So, my read on the current situation is that jonringer can't really be a release manager this time, as he got banned on multiple relevant nix* platforms. (Let's not discuss how or why, at least not in this channel.) | 06:00:38 |
| Weijia | So... Let's make a second call for release manager? | 06:13:50 |
|  @djacu:matrix.org joined the room. | 06:19:12 |
|  Mic92 joined the room. | 06:38:31 |
 lassulus | I heard Mic92 wants to do it | 06:39:09 |
| Vladimír Čunát | Either way, I see the RM role as primarily coordination. So if you find some important 24.05 stuff that needs to be done, try getting others do it rather than exhaust yourself on everything. | 06:39:22 |
| Vladimír Čunát | I tend to over-commit myself even around nix*, so I don't think I should apply for 24.05. (I was RM a few years ago, BTW.) But I'll try to help with whatever individual stuff; it's just a matter priorities among various nix* work. | 06:39:36 |
| Mic92 | Hi. Where can I sign up for the role? | 06:48:53 |
 tomberek | It's normally in the announcement: https://discourse.nixos.org/t/24-05-call-for-release-manager-editor/42195 | 06:58:51 |
| tomberek | * It's normally in the announcement thread to self-nominate: https://discourse.nixos.org/t/24-05-call-for-release-manager-editor/42195 | 06:59:09 |
