IMO, the Gogs dev was correct. If you look at that community input and what Gitea became, I was glad to use the version that rejected it.
But I don’t know how it compares with Forgejo.
Comment on Recommendations for a version control system
AbidanYre@lemmy.world 3 days ago
Gogs is the original. Gitea is a fork because the dev of Gogs wasn’t taking community input (I think that was the reasoning behind it). Forgejo is a fork of gitea because some folks didn’t like gitea forming a for profit corporation (Or something to that effect).
As far as day to day use they’re all fairly similar, though it’s been a long time since I used Gogs.
IMO, the Gogs dev was correct. If you look at that community input and what Gitea became, I was glad to use the version that rejected it.
But I don’t know how it compares with Forgejo.
It’s Gitea with some security fixes and community input, as open source software should be.
what’s the problem with gitea? I never used gogs so I can’t compare it
The added features made it harder to deploy, came with some bugs, and overall traded a simple design for community-oriented features that IMO were a negative value overall.
made it harder to deploy? Isn’t it still just a single binary, a config file and a directory for data?
bugs are inevitable for evolving software.
which community oriented features do you mean? are they in the way, or is it just that you don’t need them?
princessnorah@lemmy.blahaj.zone 3 days ago
It’s not just the for-profit corporation, there’s also governance issues. Basically, the community elected certain positions and then had the rug pulled out from them such that no elections would be held again.
Source.
AbidanYre@lemmy.world 2 days ago
Thanks, I knew there was a bit more to it but hadn’t followed it all that closely.