Several years in the making, GitLab is now very actively implementing #ActivityPub!
https://gitlab.com/groups/gitlab-org/-/epics/11247
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
First bite-sized todo on the implementation path there is ‘subscribe to project releases’.
Smart move by #GitLab; through ActivityPub they’re getting a distributed version of GitHub’s social layer.
@erlend @fediversenews Awesome! I read the thread and saw no mention of @forgefed either, do you folks know anything about these efforts?
@astrojuanlu @erlend @fediversenews I'm also a little worried so see so little mention of @forgefed, and especially the idea that it's something that will be used for some small parts later without necessarily considering compatibility from the beginning. I hope I'm just misinterpreting what's been written and that ForgeFed compatibility will be taken into account at every stage.
@caesar @astrojuanlu it’s not mentioned on that page, but there are many amicable mentions of it elsewhere in the long tail of this development: https://toot.matereal.eu/@schmittlauch/110949571279023513