Support ActivityPub for merge requests (&11247) · Epics · GitLab.org · GitLab
gitlab.com
Gitlab/ActivityPub Design Documents by @oelmekki The goal of those documents is...

Several years in the making, GitLab is now very actively implementing ActivityPub! 🙌

The end-goal is to support AP for merge requests (aka pull requests), meaning git.alice.dev can send a merge request to gitlab.com/Bob/project.git

In the most expansive version of this vision, anyone running an AP-enabled git instance (with one or more repos) can send MRs to another instance’s repo, without having to sign up there.

For starters this will be GitLab-specific, but that’s already huge for self-hosters of GitLab who currently don’t benefit from the internal interop of the GitLab.com network.

First bite-sized todo on the implementation path there is ‘subscribe to project releases’. And yes, they are aware of ForgeFed and will likely make use of that spec for the advanced features of this epic.

Smart move by GitLab; through ActivityPub they’re getting a distributed version of GitHub’s social layer.

Hugely impactful as a way around GitHub’s moat as the de-facto social network of open source development. I follow hundreds of developers on GitHub, though mainly just to keep track of who I’ve interacted with, effectively adding them to a dev-specific address book.

I have a much harder time keeping track of non-GitHub devs on alt platforms, but if I could follow them on the fediverse that’s actually preferable over GitHub’s proprietary follow list.

Cross-posted to Mastodon: https://writing.exchange/@erlend/110949168258462158

    • @shastaxcEnglish
      8•10 months ago

      I’m not really following. Can you explain why it would be better? I’ve never had an issue using GitHub.

      • @[email protected]English
        47•10 months ago

        GitHub is a great platform, which has championed open-source for decades, now. I don’t think anybody has anything to blame them for (except people not liking the idea that AI is trained on their code, like sibling mentioned), it’s more about fears it may go bad. Because basically, it’s where most of the code of the world is hosted, it’s a single point of failure. People also have questioned the pertinence of having all open-source code hosted on a proprietary platform. And the acquisition by Microsoft also had a chilling effect on those of us who remember Internet Explorer 6’s Microsoft more than VSCode’s Microsoft.

        For those reasons, it is desirable for those who love the idea of decentralization to look up for alternatives. But even there, it’s perfectly fine to stay on GitHub, “decentralizing” doesn’t require everybody to leave. :) Plus, even when using an other forge, it’s still good to keep publishing mirrors on GitHub for visibility and discoverability, currently.

      • pjhenry1216
        6•10 months ago

        I know a big sticking point for many people is that all code on GitHub feeds into CoPilot.

        I don’t understand how this would help anyone who’s still stuck on GitHub for whatever reason to be able to escape GitHub. GitHub likely won’t support this. I guess it depends on why someone is ‘forced’ to use GitHub still. I’ve seen different reasons mentioned.