4 ms·
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
by gempir 4y ago
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=recentupdate&state=closed&labels=&milestone=0&assignee=0&poster=0 https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=...
Gitea
https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclose...
- tjoff 4y ago> 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. That seems completely irrelevant and orthogonal to the outrage though?