5 ms·

Speaking of Gitea, it is worth to point out that on the OP website they mention that Forgejo is working on implementing ForgeFed. Forgejo in turn, is a fork of

Speaking of Gitea, it is worth to point out that on the OP website they mention that Forgejo is working on implementing ForgeFed. Forgejo in turn, is a fork of Gitea. So anyone currently running their own instance of Gitea should consider keeping an eye on Forgejo. https://forgejo.org/ https://forgejo.org/

ComputerGuru 3y ago
How split is the community over this? I had front row seats to the gogs vs gitea split and it was clear that gitea had the upper hand when it came to momentum there. Is there a similar consensus now?
- xena 3y ago
  It's too early to know for sure yet.
- Macha 3y ago
  My impression is that Forgejo is at this point mostly a "swap the names" fork, along with a few features that Gitea dropped the ball on like ForgeFed. At the same time, Gitea has developed some pretty big enhancements to CI in that time so there's definitely a lot more development going on in Gitea. 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.
  - Semaphor 3y ago
    > 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.
    - sangnoir 3y ago
      > 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.
- Encrypt-Keeper 3y ago
  Forgejo is just Gitea with extra features potentially extra bolted on top.
vilunov 3y ago
Before I learned about that I usually dismissed Forgejo as an unimportant fork which will die off pretty quickly, but support of ForgeFed makes me seriously consider migrating from Gitea. I still believe that Gitea's org strategy is the right one in the long run, however.
lolinder 3y ago
Note that Forgejo is specifically planning on contributing ForgeFed upstream when they're done: > 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! https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59

ComputerGuru 3y ago

How split is the community over this? I had front row seats to the gogs vs gitea split and it was clear that gitea had the upper hand when it came to momentum there. Is there a similar consensus now?

xena 3y ago
It's too early to know for sure yet.
Macha 3y ago
My impression is that Forgejo is at this point mostly a "swap the names" fork, along with a few features that Gitea dropped the ball on like ForgeFed. At the same time, Gitea has developed some pretty big enhancements to CI in that time so there's definitely a lot more development going on in Gitea. 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.
- Semaphor 3y ago
  > 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.
  - sangnoir 3y ago
    > 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.
Encrypt-Keeper 3y ago
Forgejo is just Gitea with extra features potentially extra bolted on top.

vilunov 3y ago

Before I learned about that I usually dismissed Forgejo as an unimportant fork which will die off pretty quickly, but support of ForgeFed makes me seriously consider migrating from Gitea. I still believe that Gitea's org strategy is the right one in the long run, however.

lolinder 3y ago

Note that Forgejo is specifically planning on contributing ForgeFed upstream when they're done: > 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! https://codeberg.org/forgejo/forgejo/issues/59 https://codeberg.org/forgejo/forgejo/issues/59