KDE Developers Faced Demands for Generative AI Ban
A group called KDE for People requested a total prohibition of AI-generated content in all project components.
Updated on Sept. 23, 2026 in Artificial Intelligence
Live Poll
Should open-source projects allow developers to use generative AI tools in their software code?
A collective known as KDE for People has launched a campaign to ban generative AI from all Plasma and KDE components, citing concerns over ethics and human rights. The group seeks to prohibit AI-assisted code, documentation, and translations across the ecosystem.
Why it matters
The demand reflects growing tension within open-source communities regarding the role of AI in software development. Proponents of the ban argue that current policies fail to address the long-term harms and ethical concerns associated with automated content.
The requested ban encompasses all AI-generated code, assets, documentation, bug reports, and translations. It also specifically targets the practice of vibe-coding and the inclusion of AI coverage in community spaces like Planet KDE.
The players
KDE for People
This is a sub-community group advocating for a pro-people approach to software development and strict ethical standards regarding artificial intelligence.
KDE
KDE is an international open-source software community that develops the Plasma desktop environment and various other computing applications.
The details
KDE for People published their statement on the Kreddit subreddit and launched a website to collect signatures from the community. A thread creator previously locked a related discussion for a 24-hour cooling-off period to address internal divisions as the community weighs its stance on LLM integration.
Timeline
On September 23, 2026, the group KDE for People formally demanded an AI ban.
The Tech Race
The push to ban AI in KDE projects follows a pattern established by other open-source leaders like Zig and OBS Studio. This demonstrates a clear industry shift where community governance is increasingly choosing to prioritize human-authored workflows over emerging automated alternatives.
If adopted, the ban would require developers and contributors to ensure all code and documentation is manually created without AI assistance. This policy would standardize the development process across all Plasma components, potentially altering the speed and methodology of future updates.
The takeaway
The internal conflict highlights a fundamental debate over the value of human-authored contributions in technical projects. Developers and contributors should monitor upcoming community votes to understand how these guidelines may impact the future of their workflow.
Further reading
Explore ongoing Artificial Intelligence discussions to understand how open-source communities are navigating this technological transition.
Source note: This article includes information reported by XDA-Developers.
Live Poll
Should open-source projects allow developers to use generative AI tools in their software code?
