Yeah, the only people benefitting from the GPL IMHO are lawyers and I'm unwilling to hoist an oppressive license onto my users. Personally, I don't think it's r

Yeah, the only people benefitting from the GPL IMHO are lawyers and I'm unwilling to hoist an oppressive license onto my users. Personally, I don't think it's really open source if you're going to make me jump through licensing hoops, and if the hoops are tiny in your opinion, why have them at all? I want people to use my code, I put in the public for consumption, not for the accolades or legal battles... but that's just me. SaaS means I don't have to manage it. I can also in theory collaborate with millions of people versus closed systems like Gitea or Gogs which is what two of the providers you mentioned are built atop. Interestingly enough, both of those projects use GitHub to build GitHub alternatives. What's good for the goose is good for the gander? You could easily use repository dispatch with GitHub Actions on self-hosted runners (free) to perform builds on repos that live in other places, since the interface is basically a webhook/payload. The question is why would you? What is the benefit? All of them are using GitOps style practices for the build process, some of them just happen to be a little closer. I'll take YAML over Java/Groovy shared libraries any day of the week. I'd argue that Actions is better than most CI systems.