The media in this post is not displayed to visitors. To view it, please go to the original post.
It's claimed that @Codeberg has (will?) ban projects that are developed partly using LLM tools.
Is that correct? Then I'll have to take my donations and leave.
Troed Sångberg
in reply to Troed Sångberg • • •Said and done - just as with Github I now only have forks on Codeberg. Self hosting is always the best protection against purity testers.
git.sync.wtf from now on.
Phil
in reply to Troed Sångberg • • •Apparently that is correct.
codeberg.org/Codeberg/org/pull…
The rule is
I'm not clear on how enforcement will work.
Proposal Assembly 2026: ToU extension to prohibit LLM-extrusions
Codeberg.orgTroed Sångberg
in reply to Phil • • •@phil
Thanks - alright. That's just silly, _I_ take responsibility for the legal status and security of my own code but #Codeberg can of course institute whatever rules they wish. I think they'll be surprised at how many well known FOSS projects use LLM tools today.
I do already host my own Forgejo instance so for me personally leaving will be easy, but this is a blow to European open source where many projects will just have to leave for Github et al.
@Codeberg
Phil
in reply to Troed Sångberg • • •Kai und der Andere 🎗️
in reply to Troed Sångberg • • •you sure need a lot of letters to spell "I am stupid".
@Codeberg
Alexey Skobkin
in reply to Kai und der Andere 🎗️ • • •@troed
André Polykanine
in reply to Troed Sångberg • • •Peter Vágner
in reply to André Polykanine • •Troed Sångberg
in reply to Peter Vágner • • •These two items at the very bottom of the list meant that I removed all my (non-fork) presence on Codeberg yesterday since a few of my projects were directly affected:
* Projects written and maintained with heavy use of LLMs
* Projects heavily tied to the LLM ecosytem, e.g. LLM-written tools to ease LLM usage
It's pretty clear that the Codeberg ToU changes are simply a reflection of general AI-hatred with no actual insight into how LLM tools are used by FOSS maintainers nowadays behind it.
blog.codeberg.org/protecting-o…
@menelion @Codeberg
Protecting our FLOSS commons from LLMs — Codeberg News
blog.codeberg.orgAndré Polykanine reshared this.
Zvonimir Stanecic
in reply to Troed Sångberg • • •André Polykanine
in reply to Peter Vágner • • •Peter Vágner
in reply to André Polykanine • •André Polykanine
in reply to Peter Vágner • • •miki
in reply to André Polykanine • • •André Polykanine reshared this.
André Polykanine
in reply to miki • • •Pratik Patel
in reply to André Polykanine • • •André Polykanine reshared this.
Alexey Skobkin
in reply to miki • • •There are two problems with that:
First is simple: resources are limited and for developers of Forgejo it could not only be out of scope, but even out of their awareness.
Example of the second option is LLM usage rules some project introduce. There are a lot of controversy in this matter and despite some people claiming that it's "rather obvious that %insert_their_opinion_here%", every argument they'll give you (if they bother to) most likely will have opposing arguments. And they won't be interested in a productive discussion. They'll most likely just want to shove the thing they don't like under the rug and feel good about it.
And if this thread would be a bit more popular, I'd be ready to bet on "there's no moral AI usage" comment appearing under my comment which would've been a good proof of what I'm talking about.
P.S. A better example of trying to think about the issue is SFC recommendations:
sfconservancy.org/llm-gen-ai/l…
Although I think that they leaned a bit more into the "anti-AI" movement, they shown consideration for both sides and tried to achieve something productive and inclusive. This deserves respect.
@menelion @pvagner
LLM-gen-AI - Software Freedom Conservancy
sfconservancy.orgAndré Polykanine reshared this.