I'll be that guy: Use forgejo instead, its main contributor is a Non-Profit compared to Gitea's For-Profit owners
this post was submitted on 20 Aug 2024
160 points (90.4% liked)
Selfhosted
39435 readers
3 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Silly question but what is the problem with gitea being for profit?
I guess out of fear that we get another gitlab situation, where the open source offering has a load of key features eventually kept behind a paywall
At some point they will do a Redis or Terraform and say no more open source, pay us to use it.
All contributions are now owned by us and not by the person who wrote it.
As the other commenter already said it's an abundance of caution. GItea is already moving in the direction of SaaS and an easily self-hostable solution runs counter to that plan (Gitea is already offering a managed Cloud so this is not a hypothetical). One thing that has already happened is Gitea introducing a Contributor License Agreement, effectively allowing them to change the license of the code at any time.
Thanks, I always keep forgetting what this ones called. I use a build of gitea from before it became shit but I keep telling myself I need to change to "that better one".
If it helps, it's supposed to be a drop-in replacement.
It's a hard fork by now, but the switch should still be pretty painless.
Same. It’s been on my list for too long.
Well I learned something new today.. maybe its time to plan a migration
I think for now Forgejo is a drop-in replacement. However since they are a hard-fork, at some point in the future they will diverge enough to be mutually incompatible, so the clock is ticking on migrating.
From what I have read on the FAQ they already did a hard fork from Gitea version 1.21.11 on, which was earlier this year
https://forgejo.org/faq/#im-sold-are-migrations-from-gitea-to-forgejo-possible
There's been a hostile takeover at Gitea and it's now run / owned by a for-profit company. The developers forked the project under the name Forgejo and are continuing the work under a non-profit. See also: Their introduction post and a page comparing the two projects. Feel free to look up more, since I haven't familiarized myself with the incident all that much myself. Either way though, maybe consider using Forgejo instead of Gitea.
Hostile not quite, as it was a group of core developers. But still a shitty move, especially how it was done in secrecy and disregarding other devs and the larger community.
Perhaps not a takeover so much as a betrayal, a backstabbing? Certainly hostile to the community.
That's not what happened at all.
Forgejo is actually the one in the wrong. It's an hostile fork that exist only because 3 devs were mad that they weren't hired by the company created so that the core devs of Gitea could do it full time.
You're just repeating their lies.
The Forgejo people never "owned" Gitea.
Could you please provide some sources for that? I'd like to know more.
First of all though, there is no such thing as a "hostile fork". Being able to fork a project, for any reason, is the entire point of open source. And to be fair, not wanting to continue working for a for-profit company for free is a very good reason.
And yeah, when you suddenly turn a FOSS project that's been developed with the help of a bunch of contributors, into a for-profit company, without making a big fuss about it beforehand and allow the contributors and community to weigh in, then yeah, that's a hostile takeover of sorts, at least in my opinion. Developers gotta make money, but they could've done that by creating a new brand instead of taking over that of a previously completely FOSS project. Forgejo is preventing that exact thing from happening by joining Codeberg (a non-profit).
Try its fork forgejo instead.
Why?
In 2022, maintainers (...) founded the company Gitea Limited with the goal of offering hosting services using (proprietary) versions of Gitea. (...). The shift away from a community ownership model received some resistance from some contributors, which led to the formation of a software fork called Forgejo. From Wikipedia.
But check that it has all the features you need because it lags behind gitea in some aspects (like ci).
Doesn't matter if those features are doomed to be locked behind a paywall shortly
I intentionally do not host my own git repos mostly because I need them to be available when my environment is having problems.
I make use of local runners for CI/CD though which is nice but git is one of the few things I need to not have to worry about.
Sidenote: If you just want a nice web frontend for others to view your Git repositories, you can use cgit instead.
cool guide love stuff like this
I spent a decade as a full time Tcl developer and even I don’t use fossil.
After dealing with tcl errors trying to test sqlite, I feel I've never seen a more scathing criticism of fossil.