| 20 Sep 2022 |
 jonringer | hexa: i think you would do really well :) | 14:21:06 |
| jonringer | * I would still do the post and have hexa just throw in his name. | 14:25:41 |
| jonringer | The main thing that I want to avoid is it seeming like a bunch of stuff going on behind closed doors. I really like the openness in the nix community, and I would like that to be a consistent theme. | 15:15:16 |
 Vladimír Čunát | 👍️ So, both "seeming" and "being". | 15:24:32 |
| jonringer | Sure :) | 20:51:55 |
 Janne Heß | https://discourse.nixos.org/t/22-11-call-for-release-manager-and-editor/21861 | 21:20:24 |
| 21 Sep 2022 |
|  Winter (she/her) joined the room. | 11:49:08 |
| Winter (she/her) | Is there an example of what the release editor has to do? (Like, an example of a PR done as the editor, or something.)
I understand the role description but just want to see what that actually looks like in practice. | 11:52:11 |
| Janne Heß | In reply to @winterqt:nixos.dev
Is there an example of what the release editor has to do? (Like, an example of a PR done as the editor, or something.)
I understand the role description but just want to see what that actually looks like in practice. This one comes to mind: https://github.com/NixOS/nixpkgs/pull/174607 | 11:53:20 |
| Janne Heß | also this: https://github.com/NixOS/nixpkgs/pull/174330 | 11:53:35 |
| Janne Heß | But I guess a better source for this kind of information is Mic92 :D | 11:54:23 |
 Mic92 | @winterqt: going over the release notes and | 11:55:10 |
| Mic92 | filter out stuff and reorder things. | 11:55:21 |
| Winter (she/her) | and add missing stuff :D | 11:55:50 |
| Mic92 | I.e. making it readable. We have a lot of non-native speaker so there might be typos. | 11:55:50 |
| Mic92 | Ah, yeah. I also went over the modules to find missing ones | 11:56:06 |
| Winter (she/her) | basically just making the release notes as good/complete as they can be? | 11:56:09 |
| Janne Heß | In reply to @winterqt:nixos.dev
basically just making the release notes as good/complete as they can be? In theory it's also writing the homepage update but that didn't seem as important to me (compared to the release notes) so I just did it myself | 11:56:49 |
| Janne Heß | Pretty much this, which is also posted to Discourse: https://nixos.org/blog/announcements.html#nixos-22.05 | 11:57:04 |
| Mic92 | winterqt: if we would get to this quality of writing, that would be the gold standard I think: https://blog.rust-lang.org/2022/08/11/Rust-1.63.0.html | 11:57:49 |
| Winter (she/her) | In reply to @joerg:thalheim.io
winterqt: if we would get to this quality of writing, that would be the gold standard I think: https://blog.rust-lang.org/2022/08/11/Rust-1.63.0.html How much of this would apply to us, though? Like, what qualities do we want? I agree that the Rust notes are excellent, but not sure how much applies to us.
Do we want, say, good explanations of (not obvious) changes? Or did you moreso mean just the writing style? | 12:57:06 |
| Mic92 | winterqt: I think what they are good at is picking what changes actually matter to most people. Our past release notes were all a bit random and a big hotpotch. | 12:58:13 |
| Mic92 | So I think the release notes should start with the big changes that matters to most people followed by the various other changes. | 12:58:51 |
| Winter (she/her) | Isn't that what we do already? (at least for 22.05)
How would we want to change them? | 12:59:16 |
| Mic92 | I tried to stear in this direction but I still think the release notes could read a bit more like a blog article / story. | 13:00:34 |
| Mic92 | Which is what the rust release notes are doing | 13:00:56 |
| Mic92 | winterqt: if you want to go for this position, I would also try to join in to distribute the workload. | 13:03:01 |
| Mic92 | Often it helps if text is read by different people when iterating over it. | 13:03:17 |
| Winter (she/her) | Sure, but like, how would that apply to e.g. "PostgreSQL now defaults to major version 14"? There's not much we can add to that, unless we want to rehash their release notes.
Or would we just note that without much explanation, similar to how the Rust manual lists the other stabilized functions? | 13:04:09 |
| Janne Heß | In reply to @winterqt:nixos.dev
Sure, but like, how would that apply to e.g. "PostgreSQL now defaults to major version 14"? There's not much we can add to that, unless we want to rehash their release notes.
Or would we just note that without much explanation, similar to how the Rust manual lists the other stabilized functions? I don't think too many infos make sense for all new features but something like "We updated nix from 2.3 to 2.9" is something where more info could be added | 13:04:50 |
