1. 21
  1.  

  2. 6

    I recently switched from gogs to gitea because it is more actively developed (releases are more frequent) and it is more community driven. For gogs new versions could only be released by the respository owner and the same goes for merging pull requests IIRC, which in turn was the reason to fork gitea from gogs. I am running a gitea instance together with Drone CI to get a complete CI pipeline. Drone is not restricted to gitea and can be used with a variety of other git hosting services and it only consists of two Go binaries so the deployment is a breeze. You can find my setup for both services in this repository if you are interested.

    1. 5

      Yeah, I kind of feel as if this article missed the mark a bit. While, at the moment, the feature differences of Gitea and Gogs are fairly minimal (I honestly think the only meaningful one is that Gitea can (optionally!) ship as a single binary with assets embedded), the development workflow is radically different, and that has genuine user impact. As you pointed out, Gitea ships more often; as an admin, that’s meant in practice that I’m less likely to have a security issue or feature regression with Gitea that requires me to do a custom build. The bus factor is also key here: if Unknown got bored, then yeah, Gogs would probably continue, but they’d have to build a new developer workflow, and there’d probably be a fork fight. Gitea’s community seems sane and has demonstrated effectiveness at shipping on a regular schedule, which makes me feel much more confident.

      I remember, with Gogs, having a patch of mine just sit for months because Unknown was just out somewhere. (In fact, this absence might’ve been what caused Gitea to fork; I forget.) Yeah, the PR backlog’s longer than I’d like, but they make steady, consistent progress on it. I don’t worry about a PR going nowhere.

      1. 1

        at the moment, the feature differences of Gitea and Gogs are fairly minimal …

        Gitea has implemented a lot of new features in 1.2.0, e.g. support for (GPG) signed commits, so they now differ quite a bit featurewise. Unfortunately, there is no up-to-date comparison between both.