> make a forge
> close the forge
> want to buy github
> make a forge
> close the forge
> want to buy github
@dashie MS wants to buy GitHub?
Oh boy.
FLOSS community:
> hey let's put all our eggs in this one GitHub basket
> what could possibly go wrong
> GitHub is so convenient
Microsoft:
@codewiz @dashie There is some talk about federated issues on Gitlab: https://gitlab.com/gitlab-org/gitlab-ce/issues/44486
GitHub on the other hand clearly focuses in locking you in. If not with git history, then with issues, pull requests, wikis, and all the rest.
@codewiz @dashie hosting their own instance is not vulnerable to corporate takeover of the code hosting platform and sudden changes of policies.
It is not vulnerable to outright censorship: http://tech.slashdot.org/story/13/12/14/1618239/github-takes-down-satirical-c-plus-equality-language
We may discuss whether the project taken down was "valuable" or not, but the point stands -- GitHub should not have such a power. GitLab does not, for the self-hosted instances.
FooAtWFU writes "Some clowns and jokers over at 4chan thought it would be a funny idea to put together a web page for a programming language named 'C Plus Equality' as a parody of feminism, dismissing OOP as 'objectifying' and inheritance as "a tool of the patriarchy". But this parody was apparently...
@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 @dashie However, I feel that the git hosting part of GitLab is secondary to the social aspects.
Even if you could self-host Facebook, you'd still want to be on the instance where all your friends are.
I feel that GitLab self-hosting makes sense only for very large projects like GNOME and Freedesktop, and even those incur a small loss of visibility for not being on the larger GitLab instance.
@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.