Gusted

@maddy@tech.lgbt https://web.archive.org/web/20240401124115/https://codeberg.org/

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

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.

Do you use AI to develop open-source software or believe it's the future? Then I want to let you know that you should be using GitHub or GitLab, and if you already are using them, stay there. Do NOT come to Forgejo or Codeberg. Why?

GitLab just made it very clear that they are fully committing (they say betting on the agentic era) to the opportunity that the agentic era provides. I noticed they rebranded their homepage slogan a while ago to "Finally, AI for the entire software lifecycle." making it clear they are going to provide you with AI features (for AI). And the CEO made the realization that the slogan "Finally, AI for the entire employee lifecycle" also sounded funny and went ahead with realizing that, devaluing human employees in the process. https://about.gitlab.com/blog/gitlab-act-2/

GitHub made the rounds last year that its leadership lies with Microsoft’s CoreAI organization (https://www.theverge.com/news/757461/microsoft-github-thomas-dohmke-resignation-coreai-team-transition) and already has been widely announced to pivot to provide a platform for AI or get out. Projects leaving over it (https://ziglang.org/news/migrating-from-github-to-codeberg/)

Of course, if you use AI and think it's the future, you don't see a problem with this, right? If you do see a problem here, then you're a hypocrite. Decisions like these are directly fueled by betting that you and others will start and continue the usage of AI.

Forgejo is committed to not using AI for developing Forgejo (https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md) and has not developed features tailored for AI. I've co-authored a proposal with @gedankenstuecke@scholar.social to make Codeberg's official stance to be against AI (https://codeberg.org/Codeberg/Community/issues/2514#issuecomment-14514738).

There's literally no reason to expect your use case that involves AI will be supported by Forgejo or Codeberg now or in the future. So don't come looking or asking for it. Stay at the platforms that are CLEARLY serving this use case.

@feld@friedcheese.us @mark22k I'll propose internally to setup a mesh network of HAM radio's around the world that can broadcast the status of Codeberg's infrastructure. If DNS goes down of codeberg.org and codeberg.eu, HAM radios are clearly the last reliable resort and there's clearly no bigger issues that Codeberg (or the world) would be facing at that time.

I recently learned from @algernon@come-from.mad-scientist.club about a very useful behaviour on Github. When you visit a Github repository that a user you've blocked has contributed to, you see a warning. Now if I block github.com/claude, it's easier to see if a repository is worth checking out or not.