| 21 Sep 2022 |
Linux Hackerman | I feel like copying the enable option description would be more informative without being much more effort? | 13:23:22 |
Winter (she/her) | oh you mean like the "c is a y for a" | 13:23:23 |
Mic92 | But it was a mechanical task | 13:23:23 |
Mic92 | sometimes the enable description is helpful. | 13:24:02 |
Mic92 | But it was not always the case | 13:24:08 |
Mic92 | But either way, if not all modules get a description than we have more time to make the rest better anyway | 13:24:40 |
Mic92 | I think it would also help to set an upper bound on the length | 13:25:17 |
Winter (she/her) | Eh? If we do the module description one and done then it's not too much time wasted. | 13:25:20 |
hexa | please apply on the discourse already π | 13:25:21 |
Winter (she/her) | if you're talking to me, i was just doing that ;p | 13:25:37 |
Mic92 | Sure, it might be automateable but we would also waste the readers time. | 13:26:03 |
Winter (she/her) | Isn't that also the same with listing them all without descriptions? | 13:26:29 |
Mic92 | If it's just one compressed paragraph, that one can skip over? | 13:27:18 |
Mic92 | I think that might be worth a try | 13:27:24 |
Mic92 | winterqt: consider yourself hired :) Please post on https://discourse.nixos.org/t/22-11-call-for-release-manager-and-editor/21861 :) | 13:28:14 |
Winter (she/her) | i was writing :) sec | 13:28:32 |
Mic92 | You can add me as the previous release editor as well | 13:28:32 |
Winter (she/her) | done | 13:29:23 |
Winter (she/her) | In reply to @joerg:thalheim.io You can add me as the previous release editor as well in my post or the nomination post you mean | 13:29:35 |
Winter (she/her) | (main post) | 13:29:39 |
Winter (she/her) | I assume my post since you already are mentioned in the main one? | 13:39:21 |
Winter (she/her) |
There should always be two release managers, where each release manager serves
for two consecutive terms/releases.
this conflicts with the rest of the post/the last few releases π should it be changed? | 13:40:26 |
Mic92 | It says "release manager". I don't think we have this process for release editors yet, but I don't see any reason we should not just do the same for release notes. | 13:48:02 |
Winter (she/her) | In reply to @joerg:thalheim.io It says "release manager". I don't think we have this process for release editors yet, but I don't see any reason we should not just do the same for release notes. No, I mean that for the past few (2?) releases, we've only had one manager. | 13:48:35 |
Mic92 | There was one manager, but the previous one was still supporting the current one | 13:49:02 |
Winter (she/her) | So that should be reworded, probably...? Or maybe I'm just reading it wrong. | 13:49:35 |
Mic92 | I would leave this to janne.hess | 13:52:36 |
Winter (she/her) | Janne HeΓ: thoughts? | 13:53:12 |
Winter (she/her) | Still not sure how we'd go through and find e.g. significant module additions/changes, would it be a good idea to ask people (Discourse post) maybe? | 13:59:16 |
hexa | tig 22.05-pre..HEAD nixos/modules π | 14:00:54 |