alt Hacker NewsThe author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects.
I don't share that concern.
It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources. Personally, I have a group of friends who share a GitLab instance, for example. Are you allowed to use it? No. Why? Because I didn't go to middle school with you decades ago. Is that fair? I don't really find that question relevant. I also keep a Gitea instance running at home for all the junk that really doesn't belong on someone else's hardware. Using someone else's forge isn't the only option.
Replies
> The author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects.
Yeah, it feels so good to know my AGPLv3 free software projects are illegitimate because I haven't managed to build a community around them yet. They don't matter, they're just "one-off" individual projects. Literally prompting and shipping Fable oneshots here.
> The author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects.
I think Codeberg was never intended for one-off individual projects in the first place, such as them discouraging private repositories. Quoting their Terms of Use [0]:
> Private repositories are only allowed for things required for FLOSS projects, like storing secrets, team-internal discussions or hiding projects from the public until they're ready for usage and/or contribution. [...]
And this makes a ton of sense, because Codeberg is a community-funded volunteer-supported non-profit, and it doesn't make sense to spend their resources for repositories that don't benefit the public.
I think "legitimate contributor community" is just an excuse so I am not going to dwell on it. From Ghostty to Redis, rsync to Linux kernel, more and more FOSS projects are taking advantage of various AI tools in a responsible manner and closing the door on them is just unfortunate and backward in my opinion. We gain nothing from this change and lose a ton of progress in software freedom and digital commons.
> It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources.
Of course, and the bigger community gets to discuss their decision. :)
[0] https://codeberg.org/Codeberg/org/src/branch/main/TermsOfUse...
I do think the author is right that the Codeberg post was wrong to assert that "community" is a measure of the legitimacy of a FOSS project
A massive amount of technology runs on essentially single-contributor projects with pretty much no "community": xz, core-js, GnuPG, NTPd, OpenSSL, cURL
They didn't need to make that implication or alienate solo devs in order to drive home their point
> The author seems annoyed that Codeberg wants to focus on projects that have a legitimate contributor community and is not designed for one-off individual projects.
And the author is wrong. Nothing in the ban on heavy LLM-assisted projects + crypto and the subsequent blog post[0] is suggesting that Codeberg is against solo projects without community.
If you read the post[0] carefully and not using AI-summaries or assuming context from HN/Reddit/X comments you'll see that they are calling out specifically projects that overuse resources that are meant to be equally shared. For projects with large communities, that is expected, but solo projects with zero effective users spinning CI 20 hours a day and uploading many hundreds megabytes of code daily is just plain being an asshole.
When AI bros see words "free", they usually respond with "all for me?". But that's not how that works in most places, or atleast it's not sustainable.
Also note that Codeberg specifically said that while it's against terms, they are not going to scan for LLM-written code or pressure people to delete their small, low-resource-using repos.
[0] - https://blog.codeberg.org/protecting-our-floss-commons-from-...
I moved my projects to Codeberg 3 years ago because it promoted itself as a host for FOSS, and I was starting to think that GitHub was not going to remain a dependable FOSS host. All of mine are one-man itch-scratching that I am willing to share with others. None so far contain any LLM-assisted work.
A couple weeks ago I froze them, when https://news.ycombinator.com/item?id=48842611 came up. Not because of the LLM policy as such, but because this thread https://tldr.nettime.org/@tante/116880003584050912 convinced me that Codeberg can not be a dependable FOSS host. It's controlled by non-developers who don't have software development anywhere near the top of their priorities.
> It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources. Personally, I have a group of friends who share a GitLab instance, for example.
I think it's a bad example since your private GitLab instance wasn't all over the HN earlier screaming "are you tired of Github outages and Microslop breaking it every day? Migrate all your shit to Codeberg, the good guys of the internet" only to later pull the rug like this.
Private stuff is cool and there's place for it. Codeberg was actively positioned as an indie almost drop-in Github alternative and it's currently failing miserably at this.