Mastodawn

2 links below.

I know there was a big fight over the below, but I doubt just saying people are gonna be selfish and use it, and equating it to a thing like keyboards is the best way.

I do wish they would put up more of a fight but I guess even #Linux folk just give in to this AI nonsense. There are ways to ban it without tiring yourself out. https://github.com/torvalds/linux/blob/master/Documentation/process/coding-assistants.rst

And these folks maintain a list of projects that never use AI in their process, at all.

https://noai.starlightnet.work/

#AI #AIHype

linux/Documentation/process/coding-assistants.rst at master · torvalds/linux

Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.

GitHub

Show thread

Kawazoe 1d ago

@WeirdWriter Unfortunately, it's only possible to ban AI in coding contributions if you assume the submitter is well behaved, omniscient about their dev tools, and have good intentions. Otherwise, it's basically impossible to enforce, especially at this kind of scale.

While they'd have no way to enforce it fairly and the policy would risk being abused to silence valid contributions, I still think they should've blanket-ban it like forgeo did. At least, it would've gave them strong legal protections, compared to what amounts to a suggestion of respecting the GPL in their current policy. Now we risk loosing the whole kernel over this...

Show thread

Azuaron

@kawazoe @WeirdWriter Given that AI code is, essentially, public domain with no copyright protections, saying that "All code must be compatible with GPL-2.0-only" actually is a blanket ban against AI code. Unfortunately, it seems like they don't realize this.