After Gitlab's recent announcement I am strongly considering migrating Redox OS to Forgejo, a truly open source community maintained project.
After Gitlab's recent announcement I am strongly considering migrating Redox OS to Forgejo, a truly open source community maintained project.
@soller DO IT
CI/CD is the annoying part, but that's probably already true for you
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.
β@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.
β
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.