Eliot Berriot is a user on mastodon.eliotberriot.com. You can follow them or interact with them if you have an account anywhere in the fediverse.
Eliot Berriot @eliotberriot

This is a note to people moving their repositories blindly to Gitlab.org: do you know Google is actually a huge investor in Gitlab?

The issue is not about Microsoft buying Github. The issue is about centralization and silos.

You do not solve that by moving your data from one silo to another.

You solve that by relying on small providers you can trust, or by becoming a provider yourself.

· 138 · 91

@eliotberriot .......and we need to setup a tool/protocol to manage identities in that way, using some kind of federation, so that sharing could be as easy as with those silo.

@beaufils Yeah, it's a huge part of the problem. Distributing identities and authorization is hard, to say the least :/

@eliotberriot @beaufils OAUTH?

Anyway, without being able to create a pull request from one instance to another, self-hosted gitlab (or whatever) instances are no workable replacement for contralized platforms like github, where basically everyone already has an account and can easily contribute to other projects hosted there

BTW, gitlab has an open issue for this: gitlab.com/gitlab-org/gitlab-c

@eliotberriot yeah but at least you can spin up your own gitlab instance, github is proprietary

@Matter I'm not criticizing Gitlab: this is a great software, and vastly superior (imho) to Github in a lot of areas.

I'm talking precisely about migrating to Gitlab.org, instead of spinning a self-hosted instance or join an existing, smaller one.

@eliotberriot gitlab.com/gitlab-org/gitlab-e this is a proposal for gitlab, there are similar ones for gitea and gogs. Soon we may have a solution that suits most, and then we'll be freeeeeee

@Matter It would be for the best, yes.

Adding federation in a mature software with a huge feature set and user base (such as Gitlab) without breaking performance and security is not a trivial task though.

@eliotberriot one upside of Gitlab is that it's open, so you can stand up your own instance if Google starts pulling shit.

Not an option with Github

@jjg @eliotberriot That's true, but Gitlab is heavyweight and probably not the sort of thing you can host on an ARM board.

@bob @jjg @eliotberriot there is also gitea as a lightweight alternative FYI

@jjg please read my toot carefully: I'm explicitely talking about Gitlab.org.

I've got nothing about Gitlab the software (or the company). But the way things are going, Gitlab.org will become a new Github in the upcoming months.

@eliotberriot Sorry about jumping the gun, just a bit wound up this morning :)

@eliotberriot I've never understood why someone hasn't written a program that autosyncs your git repo with a bunch of online repositories run by different people. Then Github and Bitbucket and X would all need to collaborate to screw with your stuff.

@Canageek the difficulty is not about syncing git repositories. Git itself is pretty much decentralized by nature and designed to handle that.

But federating issues and pull requests, and authorizations, and so on... Well, that's not that easy.

@eliotberriot Right, but it seems a logical extension of gits decentralized nature, doesn't it?

@Canageek it is needed, yes. It does not mean it's an easy problem to solve though ;)

you can selfhost gitlab... or use a nive gitlab instance... anywayzzz #fuckoffgoogle

@ajeremias yes, I'm explicitely talking about their hosted solution (it says Gitlab.org in the initial toot, but I believe it's in fact called Gitlab.com now)

somehow some1 posted here that gitlab.com servers are hosted in ms azure :wicked: