Forgejo in turn, is a fork of Gitea.
So anyone currently running their own instance of Gitea should consider keeping an eye on Forgejo.
Forgejo in turn, is a fork of Gitea.
So anyone currently running their own instance of Gitea should consider keeping an eye on Forgejo.
> We're planning on merging federation into Forgejo first, then upstreaming it to Gitea.
There are other reasons to switch to the fork, but I think you'll get ForgeFed either way, which is as it should be. The more participation in the protocol the better!
The largest hosted instance, Codeberg has thrown in behind the Forgejo fork, which is the largest endorsement it has, but I think a lot of smaller instance operators are either continuing with Gitea or adopting a wait and see approach.
I think the real test for Forgejo is how sustainable it will be once the codebases diverge to the extent that it can't just rebase on Gitea for the feature work Gitea does.
The plan is to stay close enough for that not to happen, at least that’s how I understand it.
That's a shame. I have no interest in CI and other "enterprise-y" features and was hoping to side-grade to Forgejo. I run my instance on an Raspberry Pi Zero and my non-latest version of Gitea is a memory-hog as it is. I'll be giving Gogs another look.