On 25/05/2026 16:39, Tom Rini wrote: > On Mon, May 25, 2026 at 03:29:50PM +0100, Josh Law wrote: >> On May 25, 2026 3:27:18 PM GMT+01:00, Tom Rini <[email protected]> wrote: >>> On Mon, May 25, 2026 at 03:25:19PM +0100, Josh Law wrote: >>>> >>>> But most projects do generally ban AI anything. >>>> >>>> Idk what we could do for u-boot when it comes to a sashiko like >>> solution. >>>> >>>> Maybe we could talk about it? >>> >>> Proposing a policy for the project about AI (and indeed not just linking >>> to other projects which have what I find to be helpful references) is on >>> the TODO list for the project leadership committee. We've just been >>> busily handling other issues for a while now, unfortunately.
For kernel: https://web.git.kernel.org/pub/scm/linux/kernel/git/docs/linux.git/commit/?h=docs-next&id=48c3876a6a6f78578ccd0fec71ef67fd6a3fd6f5 >>> >>> >> >> I could put something into suggestion: >> >> >> So, for patches: you could do assisted bys, and it depends on the >> maintainer, etc etc like Linux, >> >> >> And for reviews: that's actually hard to think about, because some >> maintainers love using AI review tools because it's useful, others >> don't particularly like tools like that, maybe a opt-in "reviewman"? >> >> But tbh that's up for discussion. > > Thanks for offering, but it's going to be a large / contentious enough > issue that we haven't gotten to it yet, unfortunately. > Before you waste too much time, that person uses vibe coding without any control and without any supervision, so that's basically AI slop. Also, in terms of reviewing whatever review they would provide has little value. I am sure Josh Law would be happy to give "AI-slop" review and get tags for that. Best regards, Krzysztof
