<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx" -->

---
title: LLM Policies: Progress At All Costs | daily.dev
description: An opinion piece argues that the debate over LLM contribution policies in GNOME and KDE is really a clash between two visions of FLOSS: a 'collectivist' view...
canonical: https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: LLM Policies: Progress At All Costs | daily.dev
og:description: An opinion piece argues that the debate over LLM contribution policies in GNOME and KDE is really a clash between two visions of FLOSS: a 'collectivist' view...
og:url: https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx
og:image: https://api.daily.dev/og/posts/lfkng02jX.png
og:image:alt: LLM Policies: Progress At All Costs
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.

# LLM Policies: Progress At All Costs

**[Lobsters](https://daily.dev/sources/lobsters)** · 6 min read · 0 upvotes · 0 comments

## Summary

An opinion piece argues that the debate over LLM contribution policies in GNOME and KDE is really a clash between two visions of FLOSS: a 'collectivist' view that values community, mentorship, and shared journey, versus a 'completionist' view that treats FLOSS purely as a product to optimize. The author claims LLMs empower the completionist camp by letting self-styled experts bypass discussion and mentoring, producing 'expert slop' under a corporate, progress-at-all-costs mindset. The piece links this to broader externalities attributed to AI hype (climate impact, data center harms, financial speculation, pension risk) and calls for GNOME to maintain its 'Principled Software' stance by resisting LLM-driven shortcuts, referencing KDE's contentious LLM-friendly draft that was deleted amid bans and backlash.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://diegoe.be/2026/09/25/llm-policies-progress-at-all-costs>

## Questions this post answers

### Did KDE ban LLM-generated contributions to its projects?

KDE's attempt to draft an LLM-friendly contribution policy sparked a major community conflict, leading to the draft being deleted and several contributors being banned amid the backlash. The controversy highlighted deep disagreement within the KDE community about whether AI-assisted contributions are acceptable, rather than resulting in a clear, settled ban.

_Follow how open source communities are shaping AI contribution policies on daily.dev._

### What LLM contribution policies does GNOME currently have in place?

GNOME has no single official project-wide LLM policy, but several individual teams already enforce strict rules against generative AI contributions, including gnome-calendar, loupe, libadwaita, gnome-software, and the Circle app criteria. An informal draft proposing a full ban on LLM contributions across all GNOME projects and infrastructure has also been circulated within the community.

_Track evolving GNOME and KDE governance decisions on AI tooling via daily.dev._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 28 comments across lobsters, hackernews (as of 2026-09-25).

**TL;DR:** Discussion largely pushes back on the piece's framing, with many arguing the 'collectivist vs completionist' dichotomy is oversimplified or wrong, while a smaller group defends the anti-LLM, community-first stance; a side debate erupts over whether critics of LLMs need to have used them.

**Sentiment:** 10% positive · 35% mixed · 55% skeptical

**The case for**

- Some agree LLM-driven contributions risk producing low-quality 'slop' that bypasses mentorship and community process.
- A few see value in keeping FLOSS free of LLM involvement even while acknowledging productivity gains elsewhere.

**The pushback**

- Many argue labeling a non-ban proposal 'LLM friendly' is overzealous and plays into AI hypesters' hands by making critics look unreasonable.
- Several reject the idea that 'completionist' FOSS is apolitical or purely product-focused, citing Stallman's explicitly political anarchist goals.
- Multiple commenters are tired of the 'you haven't even used it' rebuttal, arguing they can judge LLM output and its effects without personally using the tools.
- Some dispute the claim that LLM productivity gains are illusory, pointing to newer models and updated research as counter-evidence.
- One commenter frames anti-LLM sentiment as partly rooted in unspoken, harder-to-articulate motivations rather than pure craft concerns.

**By community**

- lobsters (heated): A long, contentious thread split between defending the collectivist anti-LLM stance and strongly pushing back on the article's framing, productivity claims, and rhetoric.
- hackernews (mixed): Only a brief comment predicting the FOSS schism will worsen, offering too little signal for a clear lean.

**Hottest debate:** Whether it's legitimate to judge and criticize LLMs without having personally used them.

**Open questions**

- Is the 'collectivist vs completionist' framing an accurate description of the FOSS community split, or a false dichotomy?
- How much has actual LLM coding productivity improved with newer models versus the cited early-2025 research?

**Highlights**

> > I kinda disagree with calling a proposal that is not an outright ban "LLM friendly". If I were an AI hypester, I'd be positively *gleeful* at every one of these overzealous judgements passed towards projects, who try to impose limits, but not enough to pass the purity line. People, who haven't formed strong opinions yet will see the outrage, check what the actual policy was supposed to be, see that it was really not nearly as bad as it was portrayed as, and will thus put less weight behind arguments raised by antis. It's like astroturfing, but it's your own very enemies doing all the work, while you don't have to do anything.
> — [nemin on lobsters · 6 points, 1 comments](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs#c_iyjob3)

> I don't need to use something to pass judgement on it, especially when I can see its direct effects on my coworkers and peers. I'm getting really sick of this "you haven't even used it yourself" argument.
> — [dallen on lobsters · 12 points, 2 comments](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs#c_uafuub)

> > On the other side there is "completionism", where FLOSS is "just a product" and its only goal is to always be better, faster, safer. Any fun to be had is in individually solving technical problems and requirements. Social bonds may happen, but colleagues are more coworkers than community. This is a "100% allglitches alltricks" TAS speedrun. The "we are apolitical", "we only care about the code" view. This is a _deep_ misunderstanding of the "completionist" project, or at least large parts of it. The completionist project is profoundly political, dating right back to Stallman himself. The goal was to provide an operating system and a set of tools that preserved the freedom of end-users to do whatever they wanted with their computer. This is essentially an "anarchist" project, in a political sense: Devolve power to the people. Allow them to do anything they want with their hardware. And Stallman chose essentially anarchist means: Programmers would build GNU themselves, and give it away under a copyleft license, to prevent the commons from being enclosed. Under the GNU Project's goals, nothing suggests that you _couldn't_ just ask a benevolent Culture Mind to just implement the entire GNU system, document it extensively, and release it under copyleft. (Let's assume Culture Minds can legally apply copyleft to their own creations, based on the legal argument of "give the nice Rapid Offensive Units anything they want.") Boom, total end-user freedom, done in an afternoon. **A modest proposal:** Since I'm mildly annoyed with people declaring that the completionists are apolitical, I'm going to propose an even more radical completionist project. To be clear: **I do not necessarily endorse this project.** The goal: Every non-technical end user should not just have the _hypothetical_ ability to modify their operating system and applications. Instead, we want to make this ability _real_, for every user. Minimum system requirements will be 32GB of GPU-like RAM and 500 GB/s of memory bandwidth, so this project will need to wait until after the next big RAM price crash. This system would include: 1. A kernel and applications, covering ordinary user needs. 2. An open-weight coding LLM that runs 100% locally in those 32 GB of VRAM. Aim for 200W when actually running, or less, if laptop GPUs get good enough. 3. Strong "rollback" guardrails and data protection, making it easy to recover from many (but not all) common mistakes. Maybe more advanced changes to the system core would require turning on "developer mode" and reading some warnings. 4. "Skill" documentation explaining to the LLMs how to make common changes to the user's system. 5. Simple application-building frameworks for GUI, web and CLI apps which are designed to be accessible to both humans and LLMs. 6. Pointers to programming tutorials so that users can actually build some understanding, too. And skills that explain to the LLMs how to walk users through code and architecture. 7. An end-user app store for sharing sandboxed vibe slop (but only if it preserves the "four freedoms"). I'm being mean describing it as slop, but I bet people would actually love it, if it was done well. Roblox for free software, basically. Now, the user not only has the full source code to their system, they _also_ have a 100% local coding agent that they can talk to and ask to customize things. With luck, the guard rails and data protection will mostly hold up. Freedom can sometimes be messy, and this version might get messy indeed!
> — [emk on lobsters · 2 points](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs#c_pak8x3)

> > My take is that there are currently two ways of thinking about why FLOSS exists, or should exist. ... We can call one of these sides "collectivism". This frames FLOSS to be about accomplishing things together, enjoying the journey and bonds that big goals tend to create. The fun is the collective effort and challenge. ... "The journey is the destination", "FLOSS is the friends we made along the way", etc. On the other side there is "completionism", where FLOSS is "just a product" and its only goal is to always be better, faster, safer. ... Social bonds may happen, but colleagues are more coworkers than community. ... My assessment is that the collectivist framing finds FLOSS primarily a social exercise that rewards you with experiences, bonds, and ideas outside of your niche interests. Some times you even get good software as a bonus! The second framing sees FLOSS as a tool to scale the complexity > Almost ten years ago Allan Day described GNOME as Principled Software because of its commitment to always doing the right thing, ... This discussion is just another opportunity to continue to meet this expectation. I lean far more towards the "second framing" and not this author's clearly preferred first framing, and I don't believe "LLM productivity is not real"... and yet I still dislike GenAI on principle, regarding its net effect on the world as bad, and refuse on principle to program with it (although I don't bug other people's projects not to), a stance that doesn't seem to fit into this article's view of the matter.
> — [5d22b on lobsters · 1 points](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs#c_3mw6z4)

> > On the other side there is "completionism", where FLOSS is "just a product" and its only goal is to always be better, faster, safer. Correct, yes. FOSS are by and large functional works, not artistic ones. I think it isn't a good thing to put your personal social benefit over service to your users (or at least it needs a much more robust defense than saying "collectivism"). If social connections happen over FOSS, that's a nice bonus, but that's not why I've dedicated my life to it.
> — [sunshowers on lobsters · 2 points, 2 comments](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs#c_jnav5m)

**Source threads**

- [lobsters](https://lobste.rs/s/v6nizc/llm_policies_progress_at_all_costs) · 16 points · 26 comments
- [hackernews](https://news.ycombinator.com/item?id=49845406) · 6 points · 2 comments

## Similar posts on daily.dev

- [The GNOME LLM Policy That I Want](https://daily.dev/posts/the-gnome-llm-policy-that-i-want-isxrsuekw) · Lobsters · 0 upvotes · 0 comments
- [The people vs the AI overlords](https://daily.dev/posts/the-people-vs-the-ai-overlords-kduxszp2n) · Planet Python · 1 upvotes · 0 comments
- [LLM/"AI" Policies](https://daily.dev/posts/llm-ai-policies-upqcy20dl) · Hacker News · 1 upvotes · 0 comments
- [Programming used to be free](https://daily.dev/posts/programming-used-to-be-free-ceydkqepr) · Lobsters · 53 upvotes · 16 comments
- [AI in Linux](https://daily.dev/posts/ai-in-linux-rzpx1wixp) · Drew DeVault · 1 upvotes · 1 comments

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#linux](https://daily.dev/tags/linux)

[View this post on daily.dev](https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx)

```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":"LLM Policies: Progress At All Costs","url":"https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx"},"datePublished":"2026-09-25T16:32:10.756Z","dateModified":"2026-09-25T18:33:07.513Z","description":"An opinion piece argues that the debate over LLM contribution policies in GNOME and KDE is really a clash between two visions of FLOSS: a 'collectivist' view...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"Lobsters","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":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,linux","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"LLM Policies: Progress At All Costs"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/llm-policies-progress-at-all-costs-lfkng02jx#faq","mainEntity":[{"@type":"Question","name":"Did KDE ban LLM-generated contributions to its projects?","acceptedAnswer":{"@type":"Answer","text":"KDE's attempt to draft an LLM-friendly contribution policy sparked a major community conflict, leading to the draft being deleted and several contributors being banned amid the backlash. The controversy highlighted deep disagreement within the KDE community about whether AI-assisted contributions are acceptable, rather than resulting in a clear, settled ban. Follow how open source communities are shaping AI contribution policies on daily.dev."}},{"@type":"Question","name":"What LLM contribution policies does GNOME currently have in place?","acceptedAnswer":{"@type":"Answer","text":"GNOME has no single official project-wide LLM policy, but several individual teams already enforce strict rules against generative AI contributions, including gnome-calendar, loupe, libadwaita, gnome-software, and the Circle app criteria. An informal draft proposing a full ban on LLM contributions across all GNOME projects and infrastructure has also been circulated within the community. Track evolving GNOME and KDE governance decisions on AI tooling via daily.dev."}}]}
```

