> make a forge
> close the forge
> want to buy github

​

@dashie MS wants to buy GitHub?

Oh boy.

@rysiek rumors for now, but lol yeah

@dashie

FLOSS community:
> hey let's put all our eggs in this one GitHub basket
> what could possibly go wrong
> GitHub is so convenient

Microsoft:

@rysiek @dashie Well, we also seem to be putting several eggs in the GitLab basket, and larger projects host their own GitLab instance.

@codewiz @dashie comparing a solution you can self-host with a fully centralized solution is, I feel, disingenuous.

Of course we should have *more* implementations (and we do, actually), but these are problems on two different levels.

I'd like to see federated issues/pull requests between git-hosting instances thouhg.

@rysiek @codewiz @dashie I wrote up https://gitlab.com/gitlab-org/gitlab-ee/issues/4517 some time ago. I think it's viable, and quite possibly fun to do.

@lupine @rysiek @dashie Awesome proposal, and it seems feasible too!

Some time ago, an old friend of mine implemented a more radical approach to distributed git hosting: https://blog.printf.net/articles/2015/05/29/announcing-gittorrent-a-decentralized-github/

I'm not saying we should do it this way, but I love how he combined three existing technologies to produce fully-distributed version control.

@codewiz @lupine @dashie I am aware of GitTorrent and I do think this is where we should be going, long-term. However, I was under the impression it's not actively developed/supported anymore?

I'd love to learn otherwise!

@rysiek @lupine @dashie It works, but it was always intended as a proof of concept, I guess?

The hard problem, IMHO, is re-creating the full GitLab experience on top of all this. Designing a nice workflow was already very hard without throwing torrents and blockchains in the mix.