We are changing our system. We settled on git (but are open for alternatives) as long as we can selfhost it on our own machines.

Specs

Must have

  • hosted on promise
  • reliabile
  • unlikely to be discontinued in the next >5 years
  • for a group of at least 20 people

Plus

  • gui / windows integration
  • @swoooshOPEnglish
    3•1 month ago

    Is there a reason to choose gitlab over gitea?

    We do not need ci/cd

    • @[email protected]English
      7•1 month ago

      If you don’t need CI/CD I don’t see any reasons to choose Gitlab over gitea. But I’m still testing gitea so take my words with a grain of salt :)

      • MubelotixEnglish
        6•1 month ago

        Gitea also has excellent CI support with builtin compatibility with github

    • lemmyvoreEnglish
      2•1 month ago

      If you don’t need CI/CD I’m not sure why you need a centralized frontend at all. Git itself is distributed and you can setup any code flow you can think of. It has hooks that can be used to set up code quality checks on select branches. There are local history browser apps for every platform and IDE plugins.

      A frontend is no substitute for developer communication — usually what the “PR” thing does is sugarcoat the fact the devs don’t know how to use Git and/or don’t talk to each other.