Gitea 1.19
blog.gitea.io
blog.gitea.io
A lot of comments about "Forgejo". In short: meh. Not a big deal[2]. I'll be sticking with Gitea.
Disclaimer: I am a part of the Gitea project, the TOC, and am employed to work on Gitea
This is perfect for my needs. Thank you to the Gitea folks for getting this added/integrated!
Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...
I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-...
Using separate systems for working with the code, doing CI/CD and storing artifacts made each of the parts easier to update, limit the resources available to each, as well as limited the fallout when something does go wrong - say, still being able to interact with the codebase, even if the container repo is temporarily unavailable, or vice versa.
That said, in a few years I might come around to holding the opposite views again - frankly, both approaches are good and seeing the Gitea Actions project is nice! Though I'll also acknowledge that some might claim that all-in-one solutions are sometimes a bit half-baked, a criticism that I've heard of GitLab in the past (though honestly they're also fine, especially for the more enterprise settings, where you have beefier servers and a few people to manage the install).
This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.
This is horrible!
While reverse proxy auth should be disabled by default, this is critical. This breaking change makes gitea unsuitable for me going forward.
Reverse proxy auth is perfectly secure when correctly setup and is sensible in many configurations.
edit: looks like Forgejo is already talking about Actions support https://forgejo.org/2023-02-27-forgejo-actions/
I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?
Gitea will remain fully open source with no tiers.
The community TOC also has advantages in any such voting where something may negatively affect the OS project, although as you mentioned that hasn't happened yet, and I don't expect it will.
Both of them will give you nearly the same experience, and they are a soft fork so all Gitea changes will be available.
I'm biased as a community member of the Gitea TOC, so I'd of course recommend Gitea.
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/
There have been a few cases of open source collectives/coops that do what Gitea does but distribute the profits to contributors equally, wonder if any of those have reached sustainability.
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...
That seems completely irrelevant and orthogonal to the outrage though?
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.
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.
We've had the .com domain for a little while, so now we're starting to consolidate things to it.
Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.
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.
I'd hope so! I am not interested in many of the features being added to Gitea (i.e. the momentum you allude to[1]). I want a light binary I can continue to self-host on a Raspberry Pi Zero that doesn't have Docker installed.
1. I feel Gitea is being positioned as a competitor to GitHub and GitLab - good for them! However, the previous iteration was close to perfect for my needs, albeit not very monetizable. I'm glad it got forked and will be side-grading to Forgejo.
The momentum stalled when the community was plagued recently by toxic behaviour of one of the members who started the fork. He had to step down from the "well-being" team[1], bullied a moderation team member into stepping down[2] and forced him to disclose information from a private chat[3].
Now he is trying to "reboot" the community to erase his previous bad behaviour [4]
Forgejo members are also unhappy about conflicts of interest of this individual [5]
The Forgejo community is stronger than this one individual, so it will succeed.
[1]: https://codeberg.org/forgejo/meta/commit/d822fc3b90f79372023...
[2]: https://codeberg.org/forgejo/meta/issues/176#issuecomment-82...
[3]: https://codeberg.org/forgejo/meta/issues/176#issuecomment-82...
[4]: https://codeberg.org/forgejo/meta/issues/187
[5]: https://codeberg.org/forgejo/meta/pulls/180#issuecomment-843...
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.
Straining to assume good faith here but this seems very likely to be wilful misinfo - particularly given the emphasis. The reasons for the fork are very clearly stated in the lettter linked in the comment you're replying to: it's about community decision-making procedures (which have been removed during the incorporation). It's also about profit: the US corp is for-profit.
Secondly, not only are Codeberg a non-profit, they also adopted the project after the fork. That wasn't a part of the original letter nor discussion. They don't control the project (see aforementioned objections on the basis of democratic input) - they're a host & benefactor.
A quick clarification here, the new TOC is comprised of three company members and three community members, with community members having a slight advantage should there be a split vote on anything.
A small clarification, Gitea Ltd. which owns the trademark and domain is (apparently) based in China.
No, Gitea Ltd is a new _Hong Kong_ for-profit company. No American companies are involved in any of this whatsoever.
The Gitea head honcho claims to be in Shanghai, China: https://gitea.com/lunny
> not that a company took it over.
No, the Forgejo folks were angry that the previously community-run project was taken into ownership of a for-profit company, without any notice, and against previous promises: https://gitea-open-letter.coding.social
> They didn't AGPL forego
Uh, they CAN'T relicense it to AGPL or anything else. The Gitea authors and contributors still hold the copyright on the code, which is MIT-licensed.
Could someone post a link to the decision?
I think, this seems to be the discussion everyone is talking about
"This is a custom fork of nektos/act, for the purpose of serving act_runner.
It cannot be used as command line tool anymore, but only as a library.
It's a soft fork, which means that it will tracking the latest release of nektos/act."
Now I worry even more about everyone maintaining forks of everything rather than doing original development.
I wonder what differences there are between Gitea's and Forgejo's forks, and also why they couldn't work with upstream.
BTW, a colleague of mine told me that GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released. I couldn't find any note on that online. Is it true?
The protocol that Actions runners use to report logs/job statuses back to Gitea is an open protocol that maybe one day woodpecker could use it for enhanced integration with Gitea, so you could use woodpecker but have the experience be next to your code.
Disclaimer: I am listed as a maintainer of Woodpecker. I am a also part of the Gitea TOC, and am employed to work on Gitea
Not sure what you mean by that, what was it supposed to be then?
Not a lot of dog-fooding going on over there.
The main repo, however, has a lot of issues/prs/etc metadata and so migrating is a bit harder.
So far everything about it has been excellent, and it's only getting better!
Are you working on anything publicly available? I'm looking for something new to play :)
Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.