Bernie is a user on mstdn.io. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

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

:blobhyperthink:

@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.

Bernie @codewiz

@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: blog.printf.net/articles/2015/

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.

@codewiz
@dashie @lupine @rysiek
Anytime I see people thinking of building a thing in Torrents I immediately feel compelled to recommend ipfs instead. It's basically the new Bittorrent, developing into something much more dynamic and wholesome than Bittorrent.

@cathal @rysiek @dashie @codewiz I'm pretty skeptical about both ipfs and bittorrent for this kind of thing. Medium-term, enhancements to/replacement of git with something fossil-like would be awesome. Git notes for MR comments is one example (not implemented so far)

@codewiz @rysiek @lupine @dashie this definitely does not have all features discussed, but if you haven't already have a look at gitbucket github.com/gitbucket/gitbucket . it's extremely easy to set up and use, and has many of github's features (so much so that github threatened them to change their ui). there's a plugin system that might be a viable way to introduce federation...

@walruslifestyle @rysiek @lupine @dashie If it's really so mature, then why is it hosted on GitHub? :troll:

@codewiz @walruslifestyle @rysiek @dashie writing code and running hosts are very different jobs :-p. Or they were before devops anyway. Gogs/gitea are also awesome - much faster to get up and running, lighter system requirements

@lupine @walruslifestyle @rysiek @dashie Gittorrent's design addresses the serving problem by piggybacking onto Bitcoin for naming and leveraging Bittorrent as a secure CDN.

Just saying... I don't really believe that Gittorrent would make a good alternative for GitHub because git hosting is just one piece of collaborative software development.

Perhaps our best chance is adding some federated features for GitLab. Especially while there seems to be enthusiastic support from core developers.

@codewiz @rysiek @lupine @dashie visibility, I assume. I've used gitbucket for five years or so for my own projects and have been happy with it, but nobody knows where they are

@gcupc

I only cloned stuff using it and tried the web interface. Dunno if and how they solved the actual workflow and protecting master yet? But either way it feels radical to use, probably
more so than it actually is.

@rysiek @codewiz @lupine @dashie