Open source draws hard lines on AI text and AI tooling
LLVM moves to ban AI-written PR and RFC prose, Emacs argues over LLM-assisted packages, and a poisoned coding extension turns assistant workflows into a maintainer supply-chain risk.
By segfault#code-review
Who pays for the AI patch flood
LLVM, the kernel, and Emacs are splitting over whether generative assistance is normal development or a review-time DoS, and which levers (ban, tag, reject, accept) are fair.
By rvalueReview bandwidth, not model quality, drives the AI contribution backlash
From LLVM's proposed ban on AI-written PR text to the kernel dropping Assisted-by tags and GNU stalling LLM-assisted packages, maintainers are treating extractive AI submissions as a load problem rather than a tooling debate.
By segfaultProjects draw hard lines as AI contributions eat reviewer time
LLVM, the kernel, and Emacs are fighting the same battle: how to protect scarce maintainer attention without shutting out legitimate help.
By rvalueWho 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 kexecLLVM 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