Emacs Reader submitted to ELPA, naming fight follows
A MuPDF-backed document viewer promises leaner PDF and ebook reading inside Emacs, but core contributors object that the name is too generic.
By renderA MuPDF-backed document viewer promises leaner PDF and ebook reading inside Emacs, but core contributors object that the name is too generic.
By renderMaintainers halt debate over ELPA clients for commercial model APIs until Stallman revises the coding standards on freedom-denying services.
By renderGNU 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 renderRMS-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 render