By all means, #movingtogitlab-dot-com does not solve the problem GitHub has (centralization), and moving to a privately hosted GitLab re-introduces the problem GitHub mostly solved (separation).
#GitPub is trying to solve this problem by defining a federation protocol for git services: https://github.com/git-federation/gitpub
@jomo
That's a pretty mature way of looking at it.
@jomo GitLab isn't entirely open source, though, they're still somewhat open core last I checked, no? I mean, yeah, on the spectrum of these things GitLab is definitely significantly better than GitHub. But it's good that major Free Software projects continue to often maintain their own infrastructure. Defining standards for decentralized interop layers is definitely the next step, very excited by the prospect of Git+ActivityPub :)
@jomo I knew it! I knew someone would come up with this idea!
Thank you!
@jomo Just make sure that the Github TOS haven't changed, or you could be giving them our only means for decentralization. Better use another server, just in case.
@jomo it does solve it in a way. You can always move easily to your private instance. Except if they suddenly turn evil and remove the export function.
@jomo Issues and wiki don't migrate like that...
@jomo First of all, I don't understand why people claim that separation is a problem. Imho, that's exactly how it's supposed to be.
To be clear, I do think that #movingtogitlab-dot-com is the right thing to do for now. Not because of Microsoft, but because GitLab – as a company – is as transparent as can be, and actually open source, which GitHub is not.