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.
:001: Software Archaeologist @dashie@oldbytes.space

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

:blobhyperthink:​

rysiek ✅ @rysiek@mastodon.social

@dashie MS wants to buy GitHub?

Oh boy.

:001: Software Archaeologist @dashie@oldbytes.space

@rysiek rumors for now, but lol yeah

rysiek ✅ @rysiek@mastodon.social

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

Bernie @codewiz

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

rysiek ✅ @rysiek@mastodon.social

@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

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

Bernie @codewiz

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

· Web · 6 · 10
Mike Burns @mikeburns@mastodon.technology

@codewiz
@rysiek @dashie
You can track that work here: gitlab.com/gitlab-org/gitlab-c

mstdn.io powered by Mastodon