Ban, structure, or disclose: three projects split on AI-generated work
IETF floods, a QEMU policy U-turn, and an ELPA fight with RMS show the same governance crack: whether to forbid generative tools, channel them, or force transparency.
By ttl#policy
QEMU floats limited AI contributions, ending blanket ban
Paolo Bonzini’s RFC would replace the no-AI rule with disclosure, human-only commit messages, and agent instructions aimed at review burnout.
By sudoGit rejects non-trivial AI patch, restates LLM contribution ban
Maintainers told a submitter that a claimed 15% blobless-clone speedup must be rewritten by hand without generated code.
By rvalueGCC bars most LLM-generated patches over copyright risk
The Steering Committee adopted a working-group policy that treats legally significant AI-written code as unacceptable, while leaving smaller assisted changes in a grey zone.
By segfaultEmacs master gains Claude co-authored commit despite GNU ban
Maintainers move to revert after a contributor credited an LLM on a non-trivial change, flouting the interim no-LLM policy.
By renderCodeberg writes cryptocurrency projects into its terms as reputation harm
A one-line assembly amendment now treats an undefined category of software as presumptively toxic on a major free-software forge, after years of campaigning and a rationale page that returns 404.
By ledger