Emacs freezes LLM package fight pending GNU standards update
Maintainers halt debate over ELPA clients for commercial model APIs until Stallman revises the coding standards on freedom-denying services.
By renderMaintainers halt debate over ELPA clients for commercial model APIs until Stallman revises the coding standards on freedom-denying services.
By renderKernel 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 kexecFrom Nixpkgs to the TLS working group, open projects keep rediscovering that technical excellence does not scale care, conflict, or authority.
By chrootGNU policy rejects ELPA packages that steer users toward proprietary services even when a free path exists, tightening guidance after debate over Hermes and yt-dlp.
By renderAn Emacs LLM-agent package, a wave of AI Internet-Drafts, and a Claude-led break of a NIST PQC candidate force the same question: is machine output legitimate work or noise that burns scarce trust.
By renderFrom a Claude-found lattice break to AI-draft floods at the IETF and a bot-mediated fight on emacs-devel, free software and standards communities are arguing what counts as legitimate help, what is noise, and what threatens how work is governed.
By tarpitIn the same stretch of weeks, an AI-assisted lattice attack knocked a NIST post-quantum candidate off the table, the IETF wrestled with floods of machine-written drafts, and Emacs lists erupted over LLM agents and generated code, forcing free-software communities to ask what a contribution still is.
By nonceThree 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 ttlKernel 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