Cc: Romain, for insight. :-) Steve George <[email protected]> skribis:
> I don't really think this division of work makes much sense for the > long-term: we have you/Romain working on Cuirass in a professional > context, we have Chris working on QA/Info in a personal context - both > are under resourced and kinda single-points-of-failures. I wish we > could have one code-base that everyone contributed to! I wish that were the case as well! There were attempts to bridge the two approaches (before the Build Coordinator and Cuirass’ “remote worker” mechanism came into existence) but that didn’t came to fruition. And here we are, years later. :-) > This is what Chris said on IRC > (https://logs.guix.gnu.org/guix/2026-01-28.log): > <futurile>cbaines: what's the status of getting QA back towards where you had > it before? Is it do'able or are you blocked? > <cbaines>it's back in the "how long is a piece of string" territory, > I'm reluctant to try and bodge it to fit Codeberg, which means a > bigger rethink to shape it in to something that wouldn't look out of > place when used with Codeberg/GitHub > <cbaines>I spent quite a bit of time trying to get/keep things working, in > the hope that people getting value from QA would help make it sustainable, > but that didn't work > > Really throwing it out there, is there nothing we can grab from another > project? I don’t know! To me, all the options are on the table. I looked at things like Forgejo Actions too, Romain made an Action that runs ‘guix lint’ for Guix-Science, and it works, but it’s very much a hack. We have two code bases that are both nice and unfit, each in its own ways, and then a wealth of popular tools that we could perhaps connect to Guix in some ways? And then there’s also: what would I do if I were to do it from scratch? In short: there’s no perfect solution in sight, only incremental improvements, but also a feel that we could turn this boring-looking topic into something exciting that people might be more interested in hacking on—I hear there’s a great Guile library for distributed programming out there. :-) I think we need a group working on the incremental improvements, in Cuirass and in QA, and a group taking a step back and rethinking this. Ludo’.
