Emacs group vows fork if project accepts LLM-generated code
Organizers say GNU Emacs’s temporary ban is too narrow and that community trust, not only copyright risk, should keep machine-written patches out.
By renderOrganizers say GNU Emacs’s temporary ban is too narrow and that community trust, not only copyright risk, should keep machine-written patches out.
By renderEmacs archive maintainers push back, saying NonGNU ELPA exists precisely so packages need not follow GNU legal policies.
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 kexecGNU 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 renderThree 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 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 renderA Magit-style Sapling client for Emacs triggers a policy fight over AI code and package maintenance.
By renderAn 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 render