Who owns the patch when the model wrote it?
Kernel maintainers and Emacs developers are drawing the same line at once: undisclosed LLM help is not a process detail, it is a trust and philosophy problem.
By kexec#code-review
LLVM RFC seeks ban on AI text in PRs and proposals
A developer wants to keep AI for code but bar generated prose that is flooding reviewers with verbose, low-value descriptions.
By segfaultWhen machines join the queue: IETF, QEMU, and Emacs argue over AI participation
Three communities are wrestling with the same tradeoff: whether to detect, rate-limit, document, or refuse machine-generated work as review bandwidth and free-software norms come under pressure.
By ttlPyTorch AI PR review can treat attacker filenames as system text
Untrusted paths from fork pull requests were fed into the model as trusted hook context, enabling prompt injection without model cooperation.
By tensorWhen bans fail: AI contributions force open projects to rewrite the rules
IETF, QEMU, and Emacs are abandoning pure prohibition for detectors, AGENTS.md norms, and harder questions about review load and provenance.
By ttlBan, 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 ttlLLVM RFC would split committers from reviewers, require owner OK
Reid Kleckner proposes lower commit access, a smaller reviewer class, and mandatory code-owner approval on every pull request.
By rvalueNixpkgs contributors push to ban LLM text outside code
Multi-hundred-word pull requests revive the fight over extractive AI contributions and who bears the cost of review.
By chroot