Hello! On Mon, 2021-03-29 at 19:02 -0400, Mark H Weaver wrote: > This sounds theoretical. Concretely, what needs do you have that > aren't > being met by Savannah? Per-branch access control > I don't understand this. It seems to me the opposite. > > If I want to contribute to this external 'wip' branch, I need to > arrange > for access. Ditto for any other Guix committer who wants to work on > it. > That's added "bureaucracy" entailed by your approach that would not > be > needed for 'wip' branches on Savannah. Cbaines is more responsive and has much lower requirements than what the "Commit Access" for GNU Guix itself requires. It's as if we created a third party git repo for both of us Raghav and myself then collaborated there except through Cbaines's infra we get CI infrastructure for free. > On the other hand, maybe your point is that you'd like to allow > direct > commit access to this 'wip' branch by people who don't have commit > access to Savannah. If that's the goal, I find that objectionable, > because when this branch is finally merged, all of those commits will > suddenly get dumped into Savannah. That increases "risk" from my > perspective. > > I actively do not want commits getting into Savannah without an > existing > Guix committer taking responsibility for them. Your approach > effectively creates a loophole for non-committers to potentially > introduce many commits into the official Guix repository in a way > that > is likely to not get adequate oversight. Why would it not get adequate oversight? It's just an easier way to collaborate on patches, but the patchset would be sent over to guix- patches before getting merged to master or else. In general I don't agree with such gatekeeping of access to wip branches because it actively hinders the development of GNU Guix by non-committers, and many non-committers would like to get involved more but they are barred by the commit access requirement. > * * * > > I'd strongly prefer for this work to be done on Savannah. If this > were > a fringe branch of marginal interest, it might make sense to have it > elsewhere, but this is core Guix desktop work that's likely to be of > interest to a large segment (plausibly a majority) of our community. > IMO, it belongs in our official git repository. > > Thoughts? > > Mark The people that work on it now are Raghav and me, and Raghav does not have commit access yet, so that's the only way we can work and cooperate now. We don't have a choice. If and when Raghav's commit access application is approved then we can move to Savannah. I don't feel like people should be barred to contribute to that GNOME 40 upgrade because they arent an approved committer. That doesnt feel inclusive to me. If you want to work on this GNOME upgrade however, that help is more than welcome, in this particular situation probably we can work on getting Raghav's commit access application approved then your concerns will be sorted out as no other non-committer participant seemed to show up. Léo