For all those having panickily migrated their projects from #Github to #GitLab to get away from MS: GitLab just started the process of migrating to the Google cloud (GCP). Which means it won't be available in some countries (Crimea, Cuba, Iran, North Korea, Sudan, and Syria) anymore because of "legal restrictions", as #Google informed them. Hopefully none of the migrators lives in any of them: migration is running already, no access possible anymore.
Well at least you can create your own
@ami But that's not where most migrated to. It's not the software I question.
@DaD Yeah. What's really needed is federation in Gitea, GitLab etc. So everyone and his little sister could self-host, and stuff would still be found.
@IzzyOnDroid Going from Charybe to scylla
@vincentxavier Ouch, a Code Odyssee …
@IzzyOnDroid To be fair since they were previously on Azure and AWS I guess it wouldn't had changed anything in the long term.
@tcit That's another thing I said "back then": Running away from MS to a platform hosted on … MS? To be honest: I had an account on both platforms before, and still have. Still wait for a federated Gitea to "reallocate".
I moved my stuff to gitlab to ensure I had a working HEAD for my repositories.
Then I created my own go-gitea instance. It doesn't have the massive overhead of self-hosted gitlab, and it has served me extremely well ever since.
My sole complaint is their use a .io domain for the primary website:
That's a pretty double-edged sword. At least Google doesn't dance to the tune of backwards regimes.
I moved to GitLab because even among large greedy corporations, Microsoft stands out as an asshole among assholes, going out into the world to cause active harm.
Anyway, the move to GitLab is only temporary until there's a viable federated solution.
Okay, they do. The thing is, they get flak for cooperating with censorship, and they also get flak for keeping their backs straight, resulting in blocks.
If our voice is so self-contradicting, it's no wonder they just do whatever they want.
@berkes GitLab *can* be self-hosted (GitLab-CE if you want it free). But GitLab.com is *not* self-hosted. So if you want that super-easy migration without the side-effects mentioned, you'd need to self-host GitLab-CE and start the migration from your own instance.
@IzzyOnDroid gitlab.com offers backups. Which allow super-easy import in *any* selfhosted version. This is a full migration. Synching is also possible, but i've not tried that.
You *don't* need gitlab-CE for selfhosting; where did you get that idea?
@berkes Migrating to gitlab.com is NOT selfhosting. And that's what my original post was about.
But moving to gitlab *is* an improvement over github. Which you stated not to be.
Github == SAAS.
Gitlab == SAAS + easy migration to non-SAAS.
Moving to gitlab.com can be seen as a step towards better decentralisation.
@berkes Yeah, *that* I can agree to. But the second step has to follow: migrating to something self-hosted. Be it GitLab-CE, Gitea or whatever. Else: see initial toot of this thread.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!