Post #2913176

2026-05-12 02:48 UTC

In other news, you don't use AI to develop open-source software and are not betting on the future of it? Take a look at Codeberg and Forgejo. Let me list a few points, in no particular order, about what's great about Forgejo and considerations if you want to move. We would graciously appreciate it if people could lend a hand so others feel their needs are supported and met. I was happily surprised to see https://neuromatch.social/@jonny/116537372614635109 which identified a frustrating but understandable issue: there's ever-increasing talk (and user support) about Forgejo, but the amount of work on Forgejo has not scaled with it. Are you looking at moving to Forgejo but feel it's not ready yet and missing features or unsure how certain features or workflows work in Forgejo? Document it at https://codeberg.org/forgejo-contrib/moving-to-forgejo so we can help and discuss your possible migration. Forgejo Actions is great and nicely serves the needs of large projects with their unique usage of Actions. It's been nine months since the alpha warning was removed after a security audit was conducted and the Forgejo project considers it to be stable software. @mfenniak@yyc.bike and @aha@swiss.social have and are still putting tons of hours and thought into improving it (and thereby avoiding the need to follow GitHub's direction on how they envision enshittifying GitHub actions), and I'm ever so grateful for their work on this. Many projects, people and companies have cited CI as a blocker of Forgejo when it's actually perfectly capable of doing what they've been doing within GitHub and GitLab CI already. There's no one defined profile that Forgejo targets; the same codebase powers many single-user instances on a Raspberry Pi that is collecting dust and powers Codeberg, the largest public Forgejo instance. Forgejo is quite open to discussing how you could implement a feature that you need and make it usable for others and have it in Forgejo's codebase. Although if you're coming to ask for gamification features to make your manager happy, maybe consider keeping that to yourself.

Replies (1)

@Gusted@social.linux.pizza 2026-05-12 02:50

Are you looking to fearmonger about non-existing RCEs and drop a carrot disclosure (https://codeberg.org/forgejo/website/issues/839#issuecomment-14208296)? Please don't do that; contributors also want to sleep at night. Still, Forgejo doesn't need to know where its security could be tightened and hardened; we have a good list of issues with the security label for that (https://codeberg.org/forgejo/forgejo/issues?labels=79184&state=open). It does need people's valuable time to go and work on that and feel rewarded by doing that kind of work. Forgejo has localization for a good number of languages. https://codeberg.org/0ko/ has gone to great lengths to improve Forgejo in this area and is thereby allowing translators of many languages to translate Forgejo in the best way possible for their language. We do have a massive bias for majorly translating it to European languages. At least we're not like GitHub, which is fully committed to not caring about this at all (https://github.blog/news-insights/the-library/github-in-your-language/). We gladly welcome new translators for any language and help in making an RTL layout in Forgejo. https://forgejo.org/docs/latest/contributor/localization/ We build official Forgejo (Runner) binaries for x86_64 and ARM64, but we only have CI tests on the x86_64 architecture. There's no opposition to starting to test arm64 and producing binaries for RISC-V if Forgejo had their hands on a server with that architecture. Unfortunately with AI-caused resource speculation, getting hands on affordable new hardware is challenging, even renting is seemingly no longer a viable option. https://matrix.to/#/#forgejo-infrastructure:matrix.org

Open ##2913177