I like #Forgejo more than #Gitea.
#FreeSoftware #development #Git #forge #meme #doge
26 comments
@Wuzzy I will keep this in mind, if gitea ever causes me too much of a headache I will replace it.
@Wuzzy https://translate.codeberg.org/projects/forgejo/forgejo/sl/ I have already made it to 533 strings @Wuzzy I agree. I maintained a number of Gitea environments for years in production and migrated other systems over to it in enterprise settings. I migrated them all to Forgejo last year without a single regret. @owzim@mastodon.social @Wuzzy@cyberplace.social @Codeberg@social.anoxinon.de They did, until Gitea was taken over by the Gitea Ltd for-profit at the end of 2022. Then Codeberg forked it as Forgejo. https://gitea-open-letter.coding.social/ TLDR; some trademark shenanigans by a for profit company that now owned gitea. From then on, their for-profit agenda have made gitea into a gitlab-like "open-core" thingy instead of the open source mission that they should've had since the start. Honestly, they should've relicensed the whole project as AGPLv3 (or something similar) to avoid anymore closed sourced troubles that might happen in the future. @Wuzzy and neither of them have batch import or mirror from Gitlab or GitHub. I am not importing 100s of repos 1 by 1. While true, doesn't Gitlab have an API you can leverage? It's not like you would literally be forced to click through every single one. @ascott @Wuzzy sure, but lately I haven't had a whole lot of time to write scripts to automate it. Work, toddler, newborn, planning move to Europe. It doesn't leave time to write scripts for providers. Plus I feel like with Forejo Integration could create a button press solution. It's why I ended up choosing Gitness to do my backups and self-hosted repos. Has batch import. Was done in 2 mins @Wuzzy I tried running the Forgejo web frontend on my local machine and wasn't impressed, most notably because of the high baseline CPU usage. That said, the people at Codeberg do great work. |
@Wuzzy Also don't forget to mention that the for-profit organization owning Gitea decided that all non-Gitea copyright headers in all "new" files have to be removed in order for being merged. (We all know what this leads to!)
https://github.com/go-gitea/gitea/blob/c7dcb58b1d96970959a5c8ac8d3955e4b7d027df/CONTRIBUTING.md#copyright