> 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 Is Microsoft going to buy Github?
:001: Software Archaeologist (@[email protected])

51.4K Posts, 233 Following, 823 Followers · ADMIN ACCOUNT here only. she/elle; Personnal : https://pleroma.otter.sh/dashie ; CMDR Otterian - Loutre a plein temps - SWL - Repairs TSF radios - Loves motorola mc68k. Eats Python and Go. Adminsys.

OldBytes Space - Mastodon
@bob @rysiek @dashie just rumours for now as far as I can see.

I hope they can't make an offer no one at github won't refuse.
@rysiek @dashie haha so true. I wrote an article about The Github threat https://carlchenet.com/the-github-threat/
The Github threat - Carl Chenet's Blog

Many voices arise now and then against risks linked to the Github use by Free Software projects. Yet the infatuation for the collaborative forge of the Octocat Californian start-ups doesn’t seem to fade away. These recent years, Github and its services take an important role in software engineering as they are seen as easy to …

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

@rysiek @dashie When it comes to git hosting, every developer still has a full copy of the history. There's minimal risk of lock-in.

Bug trackers are another story... do GitHub and GitLab let you export all bugs with comments?

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

Share events externally via ActivityPub (#44486) · Issues · GitLab.org / GitLab Community Edition

### Description While working in Gitlab developers and projects create a lot of interesting events, commits, comments, releases, etc. Each of these could be shared on social networks or other...

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

GitHub Takes Down Satirical 'C Plus Equality' Language - Slashdot

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.

@rysiek @dashie What Mastodon gets right is that you can interact with anyone in the fediverse regardless of which instance they picked.

Would be cool if GitLab allowed sending pull requests across instances, following remote projects, and so on.

@codewiz @dashie that is true. That's why I'd love to see federated issues and all of that.
@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.
Federation between GitLab instances (#4517) · Issues · GitLab.org / GitLab Enterprise Edition

### Description GitLab has ~Geo, which is a product for multi-region replication of GitLab data. This includes all database contents as well as files and repository + wiki data. Geo...

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

Chris Ball » Announcing GitTorrent: A Decentralized GitHub

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

@rysiek @dashie

Free Software Needs Free Tools
https://mako.cc/writing/hill-free_tools.html
June 4, 2010

Mako was correct. "I told ya so!"

Free Software Needs Free Tools :: Benjamin Mako Hill

@niconiconi @dashie yeah, I also did some talks about it several years ago.

Many of us saw it coming.