{"slug": "113-void-linux-packages-orphaned-following-ai-policy-dispute", "title": "113 Void Linux Packages Orphaned Following AI Policy Dispute", "summary": "Void Linux contributor Andrea Brancaleoni resigned maintainership of 113 packages after a dispute over the project's AI policy, filing PR #62482 to replace his maintainer details with the distribution's Orphaned entry; the PR was merged into master the next day. The disagreement arose from PR #62351, which upgraded Go in Void Linux from version 1.26.5 to 1.27.1, where Brancaleoni disclosed using an AI-based workflow for his package-impact analysis and another contributor said the AI-generated content violated Void Linux's contribution guidelines requiring submitted content to originate from the contributor. The affected packages, including Alacritty, Docker CLI, etcd, Kubernetes, Moby, Packer, Terraform, Terragrunt, Vagrant, and virt-manager, remain in Void Linux but now have no designated maintainer until another contributor takes them over.", "body_md": "The debate concerning the use of AI-generated content in the Void Linux project has now concluded, with a long-time contributor resigning from maintainership of [113 packages](https://github.com/void-linux/void-packages/pull/62482/changes) and thus leaving them listed as orphaned in the distribution’s package repository.\n\nAndrea Brancaleoni, filed a PR titled “[Disown maintained packages](https://github.com/void-linux/void-packages/pull/62482)” which replaced his maintainer details with Void Linux’s standard Orphaned entry in 113 package templates. The next day, the PR was incorporated into the project’s master branch.\n\nUnfortunately, some well-known tools and applications that are affected include Alacritty, Docker CLI, etcd, Kubernetes, Moby, Packer, Terraform, Terragrunt, Vagrant, and virt-manager.\n\nImportantly, the packages have not been removed from Void Linux; marking a package as orphaned only indicates it no longer has a designated maintainer and can be taken over by another contributor.\n\nThe change followed a disagreement in another PR in which Brancaleoni worked on upgrading Go in Void Linux from version 1.26.5 to 1.27.1.\n\nAs part of that effort, he published a detailed comparison of the packages impacted by the new Go release. [Brancaleoni stated](https://github.com/void-linux/void-packages/pull/62351#issuecomment-5642121267) during the discussion that he had used an AI-based workflow to carry out the analysis; on this point, another Void Linux contributor referred to the [project’s current policy](https://github.com/void-linux/.github/blob/master/CONTRIBUTING.md#ai-usage) on contributions made by means of AI.\n\nJust to note that the contribution guidelines of Void Linux permit the use of AI tools for research and learning, but insist that the content actually submitted to the project must be produced by the contributor. This rule applies not only to source code and documentation, but also to issues, PR descriptions, and comments.\n\nMoreover, the guidelines also mandate that contributors should disclose any use of AI tools and make it explicitly clear that AI review tools must not be included in PRs. The dispute was whether AI-generated text that the author had reviewed and understood could be considered acceptable under those rules.\n\nBrancaleoni said he understood and approved the material; however, another contributor made it clear that this did not satisfy Void Linux’s policy, since the content had to originate from the contributor and not be produced by an AI system.\n\nShortly afterward, Brancaleoni opened a new PR in which he gave up maintainership of his packages – 113 in total. The pull request for Go 1.27.1 was then closed, and the discussion about the package transfer was later locked and made accessible only to project collaborators.\n\nSo, what can be said in conclusion, except that this is probably not the last time an open-source project will have to draw a line over where acceptable AI assistance ends, and AI-generated contributions begin.\n\nIn Void Linux’s case, however, the practical outcome is a little concerning: 113 packages, some of them fairly important, especially for developers, are currently without a maintainer, or at least until someone else steps in to take them over.", "url": "https://wpnews.pro/news/113-void-linux-packages-orphaned-following-ai-policy-dispute", "canonical_source": "https://linuxiac.com/113-void-linux-packages-orphaned-following-ai-policy-dispute/", "published_at": "2026-09-15 13:07:25+00:00", "updated_at": "2026-09-15 13:15:26.798114+00:00", "lang": "en", "topics": ["ai-policy", "ai-ethics"], "entities": ["Void Linux", "Andrea Brancaleoni", "Go", "Alacritty", "Docker CLI", "Kubernetes", "Terraform", "Vagrant"], "alternates": {"html": "https://wpnews.pro/news/113-void-linux-packages-orphaned-following-ai-policy-dispute", "markdown": "https://wpnews.pro/news/113-void-linux-packages-orphaned-following-ai-policy-dispute.md", "text": "https://wpnews.pro/news/113-void-linux-packages-orphaned-following-ai-policy-dispute.txt", "jsonld": "https://wpnews.pro/news/113-void-linux-packages-orphaned-following-ai-policy-dispute.jsonld"}}