I’ve been on Codeberg for over a year now and the experience has been great. It has been around for a while, it’s fast, thanks to Forgejo, the self-hostable open-source software that Codeberg uses, which also offers great features.

However, it lacks a good CI/CD system. I feel like Woodpecker (the CI/CD system Codeberg uses) can’t do more complex things. Forgejo/Gitea have their own CI/CD system which is better, but Codeberg still uses Woodpecker.

But other than that, why isn’t Codeberg more widely adopted? Even privacy advocates continue to use GitHub, despite its acquisition by Microsoft. I agree with the sentiment that GitHub has a large user base, and its widespread adoption is undeniable, but I still think more people should try Codeberg or even self-host their own Forgejo/Gitea instances.

So, I’m curious to hear your perspective. What are the reasons that keep you tied to GitHub? Do the features and network outweigh the privacy concerns? Are there specific functionalities that you rely on and haven’t found elsewhere?

  • Lazycog
    26·
    4 months ago

    I would have given it a go, but reading their terms it seems they don’t like people having non-foss code there, and I would like to have both my foss and non-foss projects together on one platform.

    I’ve been thinking about self-hosting forgejo though!

    Edit: I did move from GitHub to GitLab, but don’t really wanna stay on GitLab either.

    • Ben MatthewsEnglish
      3·
      4 months ago

      Similar - I thought about codeberg for the source of my interactive climate model,
      but am not yet ready to give it a pure-foss license - might split in parts with different licenses. Could try self-hosting.

      • Lazycog
        3·
        4 months ago

        Off-topic but don’t want that link go to waste: your link is broken! (very cool project btw)

        • Ben MatthewsEnglish
          2·
          4 months ago

          Thanks, fixed! As you can see parts of the science code are already accessible via the ‘cogs’, but not yet the structural code - anyway keeps evolving, update soon.