After Gitlab's recent announcement I am strongly considering migrating Redox OS to Forgejo, a truly open source community maintained project.

https://about.gitlab.com/blog/gitlab-act-2/

GitLab Act 2

A letter to our customers and our investors.

GitLab
@soller I don't have any large, complex projects. Just smaller dataset analyses. That said, I have moved my private repos from BitBucket to self hosted ForgeJo. Painless for me so far. Though I will note that I also am hosting in Docker with nginx out front for one user instead of bare metal. YMMV
@soller Do it, Forgejo is amazing and super easy to set up, I have my own private instance and it’s super refreshing not having to deal with corpo/AI crap.
@edfloreshz @soller I'm excited about Forgejo just for the future federation... thank you for the additional recommendation

@soller DO IT

CI/CD is the annoying part, but that's probably already true for you

@soller that is some seriously inhuman corporate bullspeak. Yeah, I'd be migrating off that platform ASAP.

@soller

Just migrated off of my private self hosted gitlab instance to a self hosted Forgejo instance. So far so good - it was super easy. And I'm extra glad I did so having read that.

@soller sigh. First Sourceforge to Github, then Github to Gitlab. Now Gitlab to Codeberg. I am tired of this ****, and i am sure you are too. Least we are using Git verses mercurial across all these so there is some silver lining. Oh and SVN too, i dont remember any of the SVN stuff so i avoid sourceforge as much as i can get away with.

Goodluck with the Migration.

@Mirppc @soller if that helps, codeberg is a non-profit organization, so it cannot legally become a public company like companies behind sourceforge (in the past), github, and gitlab did

codeberg simply cannot have investors demanding more and more profits, and is instead focusing on providing actually good git repository hosting service for free software projects
​​

which effectively means that hosting projects on codeberg should be pretty stable
@sugar @soller That wasnt the point of my post. My point was the frustration of having to switch every few years because BitBucket, Sourceforge, Github, Gitlabs or other does something stupid. It is tiring.
@Mirppc @soller makes sense, faer point was that codeberg shouldn't do something stupid like that in the future, having no profit motivation to do anything like the services you mentioned ​​

@sugar @soller Oh but they can. Even FOSS communities have made bad chocies from making a terms of service require only people over 16 can even thouch a project, to dropping X86_64 V2 and older support, and whatever other controversial thing has people riled up.

Just because there isnt a profit motivation doesnt mean they cant do something that makes people upset.

@Mirppc @soller true ​​

that said, as far age requirement on codeberg is concerned, fae thinks it's unlikely unless eu laws change to mandate codeberg to verify users' age (github requires users to be at least 13 years old due to coppa, however coppa doesn't need to be complied with for entities outside of united states, and codeberg is in germany)

(mastodon.social does require users to be at least 16 years old, due to gdpr, however the requirement in gdpr that mandates that only applies to "information society services", which fae doubts code hosting services like codeberg are, and considering microsoft didn't make being 16 years old a requirement for using github, doubtful microsoft sees it that way either)

the thing about dropping x86_64-v2 is mostly inapplicable to codeberg, as it's not a software repository

also, it's worth noting about x86_64-v3 requirement, there is only one distro that made it a requirement: rhel 10 (which is owned by ibm), and that requirement is so controversial that almalinux (a fork of rhel) went out of the way to not have it:
almalinux.org/blog/2025-05-13-epel-10-kitten-v2/

in general however, if codeberg screws up badly (mistakes happen, that's okay), fae would expect people working on it to try to undo whatever happened after realizing that something was a mistake
x86_64_v2 EPEL for the Enterprise Linux 10 World

Last October, when we announced AlmaLinux OS Kitten, we also announced that we would be providing support for x86_64_v2 chips for the AlmaLinux OS 10 lifecycle. We know that many users of AlmaLinux rely on Fedora EPEL for tools and packages outside the base set of packages included in AlmaLinux OS releases. Historically, our users have been able to rely on the Fedora project entirely for those packages. However, EPEL builds against RHEL, and with RHEL 10 moving to support only x86_64_v3, EPEL will no longer cover x86_64_v2 use-cases for version 10.

AlmaLinux OS
@soller I migrated my personal projects to forgejo and have not looked back. Highly recommended!
@soller Correction: I have looked back once, because some projects like yazi's `ya pkg` tool only support github repos. But I'll work around something as petty as that before I go back.