| 8 Mar 2023 |
infinisil | Profpatsch: That's super fishy, I can't do that with good faith! | 16:49:00 |
infinisil | Going by code, only me and Robert Hensing (roberth) are authors yes, but the entire team worked together on the idea and are already in agreement about it | 16:50:26 |
profpatsch | infinisil: I’d say if you note that in a comment, I don’t see any reason why you couldn’t make up like half the shepherd team from people in this channel | 16:51:13 |
profpatsch | And if nobody else has an interest, fill the rest as well | 16:51:24 |
profpatsch | It’s not like this is a company with profit motives, the contrary | 16:51:41 |
profpatsch | Otherwise the Architecture Team kinda invalidates itself if it can’t get RFCs pushed through | 16:52:12 |
@piegames:matrix.org | I've run into this entire problem before, and the concept of "authors and shepherds are distinct" kind of fails apart for RFC that are developed by a team like this | 16:52:39 |
@piegames:matrix.org | Technically RFC 101 has exactly the same situation | 16:52:53 |
profpatsch | Maybe there should be some kind of “if you want to veto, you have to be a shepherd” | 16:53:11 |
profpatsch | Or “if you veto, you are automatically made a shepherd” | 16:53:21 |
infinisil | In reply to @piegames:matrix.org Technically RFC 101 has exactly the same situation Oh yeah, it's now the shepherds working on the RFC.. | 16:53:35 |
@piegames:matrix.org | Yep | 16:53:47 |
profpatsch | I feel like the process is now actively hindering productive changes | 16:54:07 |
@piegames:matrix.org | Yet another way our RFC process is fundamentally broken ^^ | 16:54:17 |
infinisil | So, is this RFC blocked on making a separate RFC to change the RFC process to allow authors to be part of the shepherd team? | 16:54:22 |
profpatsch | no | 16:54:28 |
profpatsch | I’d say just mention it, and proceed | 16:54:39 |
profpatsch | Then you can always said you mentioned the problem and nobody veto’d | 16:54:52 |
profpatsch | s/said/say | 16:55:04 |
infinisil | Hmm that might work yeah, will have to be properly talked about with the steering committee though | 16:55:15 |
@piegames:matrix.org | No, but eventually we'd have to fix our process to better match reality. And the RFC-in-repo thing is definitely a first step towards that (even though I personally don't agree with the direction it's taking) | 16:55:32 |
infinisil | And get an official special pass for that RFC | 16:55:40 |
profpatsch | infinisil: maybe start a parallel discussion on discourse | 16:55:44 |
profpatsch | And mention it from the RFC | 16:55:50 |
profpatsch | Also <insert Grace Hopper quote about forgiveness here” | 16:56:43 |
infinisil | In reply to @piegames:matrix.org No, but eventually we'd have to fix our process to better match reality. And the RFC-in-repo thing is definitely a first step towards that (even though I personally don't agree with the direction it's taking) We just had a meeting on that on Monday, see meeting notes here: https://discourse.nixos.org/t/2023-03-06-rfc-138-developing-rfcs-in-repositories-meeting-1/26075, we also need another shepherd for that RFC though, and you seem interested, how about nominating yourself? :D | 16:57:06 |
@piegames:matrix.org | In reply to @infinisil:matrix.org We just had a meeting on that on Monday, see meeting notes here: https://discourse.nixos.org/t/2023-03-06-rfc-138-developing-rfcs-in-repositories-meeting-1/26075, we also need another shepherd for that RFC though, and you seem interested, how about nominating yourself? :D I think Winter already asked me, but I'm already struggling to get RFC 127 (package warnings) over the finish line, so I can't take even more work | 16:58:05 |
infinisil | Ah right, I remember now, no problem :) | 16:58:19 |
infinisil | In reply to @profpatsch:augsburg.one infinisil: maybe start a parallel discussion on discourse That's an idea, I'll think about it | 16:59:06 |
| 9 Mar 2023 |
| zmitchell joined the room. | 16:05:25 |