• dukk@programming.dev
      link
      fedilink
      arrow-up
      14
      ·
      11 months ago

      They’re both pretty on par for the most part. If it’s too much of a hassle, there’s no real need to switch.

      Now that Gitea is owned by a for-profit company, people are afraid that they’ll be making anti-user changes. This, Forgejo was born. It pulls from Gitea weekly, so it’s not missing anything. It’s also got some of its own features on top, but they’re currently pretty minor. Also, most of the features end up getting backported back to Gitea, so they’re mostly on par with each other. However, many features find themselves in Forgejo first, as they don’t have the copyright assignment for code that Gitea does. Additionally, security vulnerabilities tend to get fixed faster on Forgejo. They are working on federation plans, however, so we’ll see how that pans out.

      Overall, there’s no downside of switching to Forgejo, and you’ll probably be protected if Gitea Ltd. makes some stupid decisions in the future. However, at the moment, there’s no immediate advantage to switching, so you can stick with Gitea if you’d like.

      • PlexSheep@feddit.de
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        I thought gitea was doing federation too? Im pretty excited about that part, as I’ve wanted to move away from GitHub but the visibility it gives is just on another level. Users can’t register on my instance, therefore they also can’t open issues and PRs.

        Is switching to forgejo more work than just changing my compose file a little? I hope my database can get transferred.