Kernel selftests, QEMU policy drafts, review-bot injection risks, and Free Software fights over LLM packages are forcing projects to replace unenforceable AI prohibitions with explicit rules while licensing and security stakes remain open.
By kexecUntrusted files opened in modes other than Emacs Lisp can still trigger arbitrary code via flymake.
By tarpitIETF, QEMU, and Emacs are abandoning pure prohibition for detectors, AGENTS.md norms, and harder questions about review load and provenance.
By ttlIETF 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 ttlRMS-era ELPA provenance fights and the WIMSE push to adopt AI-agent auth drafts are one problem seen from opposite ends: FOSS still has no common norms for synthetic code or for agents as delegatable identities.
By renderEmacs package review and a Git treewide migration have forced the same unresolved fight into the open: whether AI-assisted code can carry a meaningful DCO, must be labeled, or should be refused as routine practice arrives.
By renderA Magit-style Sapling client for Emacs triggers a policy fight over AI code and package maintenance.
By renderCrafted remote-style file names can execute arbitrary local commands during connection setup, with no successful remote login required.
By tarpitOpening a crafted file can run attacker code; upstream fixed it and Gentoo backported to 28.2.
By nonceFrom standards text and theorem provers to kernel selftests and release cadence, open source is arguing over what machine authorship changes about responsibility.
By ttlAn Emacs frontend for a free agent harness draws fire over install defaults that steer users toward commercial model APIs.
By renderMaintainers settled on a repository instruction file telling coding agents to analyze only, after debate over tone, effectiveness, and optics.
By renderCoordinators want a release candidate soon, but developers say shipping another major version with a known arbitrary code execution hole would be reckless.
By renderSavannah maintainers force-reset the branch after a commit unintentionally credited Claude, leaving local clones needing a rebase or hard reset.
By renderMaintainers move to revert after a contributor credited an LLM on a non-trivial change, flouting the interim no-LLM policy.
By render