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.
@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 :/
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: https://gitlab.com/gitlab-org/gitlab-ce/issues/4013
@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 https://gitlab.com/gitlab-org/gitlab-ee/issues/4517 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
(I went with docker for some reason, rather than my usual vm style deployment... but as it's a single executable even that should be easy - point it at your database and go.)
Various other places have info on self-hosting it like https://lollipopcloud.solutions/ who are here as @cloud (I think.) I didn't use their setup, but know some who have...
Personally I’d like to see things like issue tracking and wikis be handled as a file convention within the repo itself. So forks automatically pull the state of affairs at that point in time and merges merge in changes to them.
@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 :)
@jjg that's fine, don't worry!
@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 ;)
@eliotberriot Or it would be solved already.
@eliotberriot I second the second option!
@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:
@eliotberriot my dream : a federated gitlab/ whatever for pull requests bug reports, stars etc
@eliotberriot I recommend setting up a server on DigitalOcean and slapping gittea on to it
Well put. I like sr.ht for that.
@eliotberriot GitLab, like Google and unlike GitHub, lets you download all your data; unlike Google, the GitLab app is also free software, so you can use the downloaded data to self-host what you were previously sharecropping
I guess you need to choose your silo these days. Self-hosting appears better, but in reality just appeals to a different (and arguably more frightening) set of providers.
Hosting stuff in AWS is appealing to a much more terrifying entity than Google, imo. The companies that we lease lines to the internet from are also quite terrifying.
@eliotberriot Why is that ? Maybe stumbled upon while searching ?
@mcread I don't know why, but I'm suddenly getting a lot of feedback on this post since yesterday, and it's a bit weird
@eliotberriot well that can only mean you posted too much yesterday ;)
@eliotberriot Or maybe more than usual ... I guess that's the problem : a break in routine, a distortion in the matrix ;)
@arbocenc this very old toot refers to the hosted version of gitlab.
The fact that the underlying source code is open does not really change the fact that a single platform hosting thousands of projects is a silo.
I'm not talking about self-hosted Gitlab instances here.
Or make it federated!
@eliotberriot On the plus side for Gitlab, the source code is available so if Gitlab starts going bad, you can just self-host. I think that's the only reason to use gitlab over github. That's why I use Newsblur instead of the various other RSS readers as well, available source means self hosting is possible worst case.
@eliotberriot "But THIS centralized platform will be different from the last thirty thousand!"
mastodon.eliotberriot.com is one server in the network