Hello, Hugo Buddelmeijer via "Development of GNU Guix and the GNU System distribution." <[email protected]> skribis:
> The `openshot` package was not building on the python-team branch. I > spent 20 minutes on it, and couldn't figure out what was wrong, so I > asked Codex. It took codex 1m17s. I tried to build the package 7 > times, codex 2 times. I have no doubt LLMs would perform better than me on this task because I’m clueless on ‘openshot’. :-) For a package in my field though, I may well do a better job than an LLM, in particular anticipating planned changes in our packaging strategy or upstream and providing links to primary sources explaining the reason for the change. > The P.R., with the included codex output is here: > https://codeberg.org/guix/guix/pulls/8736 > > I suggest that you first fix the package yourself, and only then look > at the P.R., because then we can merge one of your fixes instead, so > we don't 'taint' the repository. > > Could one of the sponsors of the GCD (or anyone) specifically explain > what was wrong here? I see 537 commits; if that’s intended, then nobody can realistically review it, which is enough of a reason to reject it (whether or not it’s genAI-generated). If it were changing less than 15 lines of code (thus not being “legally significant”), it’s OK for inclusion, per the current GCD draft. If it were more than 15 lines (and being evidently “creative”), then it would have to be rejected, per the current GCD draft. > What should have been done differently? I would probably have figured > out what the problem was myself given enough time, or otherwise I > could have asked Nicolas and Sharlatan, and I see there is value in > both. But enough value? I doubt it. I think the community is the project’s strongest “asset”. I would have encouraged you to talk to Nicolas, Sharlatan, or anyone whom you think can help because we’re in this together; bottom line is that you do what you want, of course. Thanks, Ludo’.
