!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

232 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture53 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
20 Mar 2023
@qyliss:fairydust.spaceAlyssa RossSo I'm happy :)21:03:56
@qyliss:fairydust.spaceAlyssa RossAnd I am still committed to getting consensus for the Rust change21:04:14
@qyliss:fairydust.spaceAlyssa RossAnd that will involve talking to everybody who raised concerns about it, either as part of NAT or otherwise, and trying to get them on board.21:04:41
@infinisil:matrix.orginfinisil
In reply to @raitobezarius:matrix.org
internal consensus to NAT team → RFC consensus
That's the current idea yeah, though the RFC process has some flaws and is very very slow, I think infeasibly slow in the long run. At some point I'd like to propose that we (the entire community) can have something like fast-track RFCs, where we just create PR's with RFC-like descriptions to Nixpkgs, and announce those PR's the same way an FCP is announced (we can even pin the PR to the top!), with the same minimum waiting period. Just an idea for now though
21:06:01
@qyliss:fairydust.spaceAlyssa RossI think that having (earned) authority reside with open and accountable teams is going to be very healthy for the sustainability of Nixpkgs21:06:15
@infinisil:matrix.orginfinisilOh and those PR's would of course have to be done and reviewed by a team of people (ilke the current RFCs require)21:06:41
@raitobezarius:matrix.orgraitobezarius
In reply to @infinisil:matrix.org
That's the current idea yeah, though the RFC process has some flaws and is very very slow, I think infeasibly slow in the long run. At some point I'd like to propose that we (the entire community) can have something like fast-track RFCs, where we just create PR's with RFC-like descriptions to Nixpkgs, and announce those PR's the same way an FCP is announced (we can even pin the PR to the top!), with the same minimum waiting period. Just an idea for now though
I am definitely interested into fast track RFCs :)
21:07:08
@qyliss:fairydust.spaceAlyssa Rossyeah that sounds like a promising direction21:08:13
@infinisil:matrix.orginfinisilAnd of course I'd go through the RFC process itself to propose changes to it :)21:08:29
@infinisil:matrix.orginfinisilRelevant: https://github.com/NixOS/rfcs/pull/13821:08:38
@qyliss:fairydust.spaceAlyssa RossI love that idea too21:09:45
@qyliss:fairydust.spaceAlyssa Rosshaving RFCs on single PR threads is absolutely horrible21:09:59
@qyliss:fairydust.spaceAlyssa RossI always wanted to move them to discourse, but having them in repos is even better I think21:10:09
@infinisil:matrix.orginfinisil Alyssa Ross: We do need a shepherd for that RFC :P 21:11:41
@qyliss:fairydust.spaceAlyssa Ross In the last week I've been nominated for a shepherd team and joined the moderation team, so I think I need to make sure I can keep up with those commitments before I take on any more :P 21:13:03
@infinisil:matrix.orginfinisil We did already have a meeting with the 2 shepherds (and me as an author), the third shepherd had to step down though due to time constraints. But I can say that this has been the cleanest and most focused RFC discussion I've experienced so far, especially withLinux Hackerman as a shepherd! 21:13:19
@qyliss:fairydust.spaceAlyssa Rossi too am a linus fan21:13:48
@infinisil:matrix.orginfinisilIn any case, feedback appreciated, there are unfortunately some downsides to the repo approach21:13:55

Show newer messages


Back to Room ListRoom Version: 9