--- title: Void Linux Maintainer Orphans 100+ Packages Over AI... description: Void Linux contributor Andrea Brancaleoni orphaned over 100 packages he maintained after a dispute over the distro's AI usage policy. The trigger was a comment... canonical: https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute | daily.dev og:description: Void Linux contributor Andrea Brancaleoni orphaned over 100 packages he maintained after a dispute over the distro's AI usage policy. The trigger was a comment... og:url: https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv og:image: https://api.daily.dev/og/posts/LyIveNvNv.png og:image:alt: Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute **[Phoronix](https://daily.dev/sources/phoronix)** · 3 min read · 0 upvotes · 0 comments ## Summary Void Linux contributor Andrea Brancaleoni orphaned over 100 packages he maintained after a dispute over the distro's AI usage policy. The trigger was a comment he posted using GLM-5.3-Flash plus OpenCode to compare Go 1.26 to 1.27 package upgrade results, without disclosing the AI usage upfront, which another maintainer flagged as violating Void's contributing policy requiring disclosure of all AI tool use. In response, Brancaleoni disowned his packages, including notable ones like Alacritty, Clementine, Kubernetes, several Docker-related tools, fscrypt, and Intel Thermald, leaving them unmaintained unless other contributors step in. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did a Void Linux maintainer orphan over 100 packages? A contributor named Andrea Brancaleoni disowned maintenance of 113 Void Linux packages after another maintainer questioned an AI-generated comment he posted comparing Go 1.26 to 1.27 package upgrade results. He had used GLM-5.3-Flash plus OpenCode without disclosing it upfront, which conflicted with Void Linux's contributing policy requiring disclosure of any AI tool usage in contributions. _Anyone tracking open source governance shifts around AI use can follow disputes like this on daily.dev._ ### What does the Void Linux contributing policy say about using AI tools? Void Linux's policy states all contributions must be made by humans, though AI tools may be used for research and learning as long as the contributor understands and originates all content, including code, docs, issues, and comments. All AI usage must be disclosed, AI review tools are barred from pull requests, and AI translation tools are allowed only to bridge language barriers. _Developers weighing AI disclosure rules in their own projects can compare policies like Void Linux's on daily.dev._ ### Which notable Void Linux packages became orphaned after the maintainer dispute? Notable packages left orphaned include Alacritty, Clementine, binfmt-support, fscrypt, Kubernetes, several Docker-related tools like docker-cli and docker-gen, and Intel Thermald, among 113 total packages disowned by the maintainer, unless other Void Linux contributors step up to take them over. _Void Linux users relying on these tools can watch for new maintainers stepping in via daily.dev._ --- Tags: [#open-source](https://daily.dev/tags/open-source), [#linux](https://daily.dev/tags/linux), [#ai-governance](https://daily.dev/tags/ai-governance) [View this post on daily.dev](https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute","url":"https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv"},"datePublished":"2026-09-12T15:17:26.599Z","dateModified":"2026-09-12T15:21:07.391Z","description":"Void Linux contributor Andrea Brancaleoni orphaned over 100 packages he maintained after a dispute over the distro's AI usage policy. The trigger was a comment...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/aad4dc0ab4b3b99aa3ced6eefd39bc37?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/aad4dc0ab4b3b99aa3ced6eefd39bc37?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Phoronix","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Phoronix","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6a26ba379dd64932830aa0c9803dd7ee","url":"https://daily.dev/sources/phoronix"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,linux,ai-governance","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Phoronix","item":"https://daily.dev/sources/phoronix"},{"@type":"ListItem","position":3,"name":"Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/void-linux-maintainer-orphans-100-packages-over-ai-policy-dispute-lyivenvnv#faq","mainEntity":[{"@type":"Question","name":"Why did a Void Linux maintainer orphan over 100 packages?","acceptedAnswer":{"@type":"Answer","text":"A contributor named Andrea Brancaleoni disowned maintenance of 113 Void Linux packages after another maintainer questioned an AI-generated comment he posted comparing Go 1.26 to 1.27 package upgrade results. He had used GLM-5.3-Flash plus OpenCode without disclosing it upfront, which conflicted with Void Linux's contributing policy requiring disclosure of any AI tool usage in contributions. Anyone tracking open source governance shifts around AI use can follow disputes like this on daily.dev."}},{"@type":"Question","name":"What does the Void Linux contributing policy say about using AI tools?","acceptedAnswer":{"@type":"Answer","text":"Void Linux's policy states all contributions must be made by humans, though AI tools may be used for research and learning as long as the contributor understands and originates all content, including code, docs, issues, and comments. All AI usage must be disclosed, AI review tools are barred from pull requests, and AI translation tools are allowed only to bridge language barriers. Developers weighing AI disclosure rules in their own projects can compare policies like Void Linux's on daily.dev."}},{"@type":"Question","name":"Which notable Void Linux packages became orphaned after the maintainer dispute?","acceptedAnswer":{"@type":"Answer","text":"Notable packages left orphaned include Alacritty, Clementine, binfmt-support, fscrypt, Kubernetes, several Docker-related tools like docker-cli and docker-gen, and Intel Thermald, among 113 total packages disowned by the maintainer, unless other Void Linux contributors step up to take them over. Void Linux users relying on these tools can watch for new maintainers stepping in via daily.dev."}}]} ```