I remember there being a big stink about Gitea, so much so that it was forked: https://news.ycombinator.com/item?id=34011581
I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?
Gitea 1.19
11–20 of 87 posts
Re: Gitea 1.19
#12For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
The issue is Forgejo doesn't really have the know-how or capabilities to drive this project forward.
In the past months all they have done is rebrand Gitea and some minor fixes, but upstream (gitea) has added a huge number of features and merged tons of valuable pull requests. So are they just going to continuously merge upstream into their fork and do nothing besides that?
The platform, Codeberg might be "well" funded but not to maintain another extra project and develop new features for it.
I think the outrage was a little too big initially. It's a big task to create a git host that needs to compete with Github and the likes and I think it's fair that you want to make some money on the side with that.
Compare these merged PRs:
Forgejo https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=...
Gitea https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclose...
Re: Gitea 1.19
#13As a novice at self-hosting, I previously attempted to use it, but got stuck as I didn't understand MySQL, and learning it just for Gitea was too much. However, I've had some progress with with another database recently, so I would like to give Gitea another try soon.
For small personal deployments, using SQLite as a database is usually sufficient. This means you don't need a fullblown SQL server, instead the whole database consists of a single file.
Re: Gitea 1.19
#14For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
I'm one of the community members on the Gitea TOC.
Just to clarify, only one maintainer left the project to my knowledge, although a few other contributors did as well. The majority of us remained with the Gitea project.
Re: Gitea 1.19
#15[flagged]
That’s a pretty strong statement to make without backing it up with some evidence of foul play, or at least evidence of these links.
Re: Gitea 1.19
#16For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
From what I, as an outsider, could see, it seemed like most contributors stayed with gitea.
At this point forgejo is just a soft-fork as well, so there really isn't any reason or hurry to switch (yet) in my opinion.
Though it did stand out that they are migrating stuff from gitea.io to gitea.com, as mentioned in this blog post.
Re: Gitea 1.19
#17For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
>and some (a lot?) of the community/devs went to https://forgejo.org/
The Forjero commits prove that this is incorrect (they are still busy removing Gitea branding related things from their code). It's going to take a long time until they begin to match the Gitea momentum.
Re: Gitea 1.19
#18For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo
It's a soft fork though, so the Forgejo folks are still relying on the Gitea team for features like this.
The Forgejo folks seem to object to Gitea on the basis that a company took the project over. I think it was that an American company took it over, not that a company took it over. They didn't AGPL forego, they just soft forked and backed the fork with a European organization instead of an American one, Codeberg[1]. Yes, the org is non-profit, but it still smacks as hypocritical.
I'll be sticking with Gitea for the foreseeable future.
Re: Gitea 1.19
#19I remember there being a big stink about Gitea, so much so that it was forked: https://news.ycombinator.com/item?id=34011581 I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?
Gitea was taken from a community run project to an corporate owned one to allow for an open core future. Currently there's been no actions taken that negatively affect the open project, but the door is now open for a "This isn't working for our company, we're now going to SSPL" style move in the future.
Re: Gitea 1.19
#20I remember there being a big stink about Gitea, so much so that it was forked: https://news.ycombinator.com/item?id=34011581 I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?