this post was submitted on 21 Apr 2025
36 points (100.0% liked)
Programming
19722 readers
125 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not sure if its better, did both and i havent noticed much difference. Forgejo runs codeberg though and is maintained by them. Also has CI with forgejo actions.
And Gitea has Gitea Actions. The big difference - and also the sole reason ForgeJo was forked - is that Gitea has a business behind it that allows them to sell support hours to other businesses. And then use the money to progress Gitea. Similar to how Zabbix and others do it. But the community decided that this is a bad thing and moved to ForgeJo.
gittea ltd was founded without adhering to the governance model gittea had and also claimed copyright on atleast the name and logo of gittea. many felt a non-profit would be a better way to organize development and thats how codeberg e.v. came to be.
the problem is not, and never was offering support and service against money, you can right now start selling forgejo if you'd desire to, it was allways about how the project itself should be organized.
While a non-profit sounds very honourable, I personally think Gitea has the more future-proof model. In fact, Gitea Actions was something they got commissioned for and were allowed to open source it as well.
This is basically how I think about it. (Not my comment.)
But we’ll see…