jomo

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

forgefed/forgefed

An extension to ActivityPub for web-based Git services federation. - forgefed/forgefed

Jun 5, 2018 at 10:58pmWeb
Show threadjomoJun 5, 2018
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.
Show threadCybre RickJun 6, 2018

@jomo I knew it! I knew someone would come up with this idea!

Thank you!

Show threadUlrich LintlJun 6, 2018
@jomo Well, but as long as #GitPub does not run on it's own platform, for now it should immediately shift from #GitHub to #GitLab. Anything else would severly damage it's credibility!
Blockchain und Blasmusik (@[email protected])

1.86K Toots, 182 Following, 1.16K Followers · Highly skilled expert computer scientist. Digital Naïve. Toots in English und Deutsch. #echterhacker https://jomo.tv

Show threadCybre RickJun 6, 2018
@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.
Show threadqwazixJun 6, 2018
@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.
Show threadjomoJun 6, 2018
@qwazix @jomo git remote set-url origin $elsewhere
Show threadqwazixJun 6, 2018
@jomo Issues and wiki don't migrate like that...