Design Discussion: ActivityPub support + ForgeFed vocabulary · Issue #14186 · go-gitea/gitea
github.com
#1612 discusses Federation in general but I wanted to open an issue for the ActivityPub + ForgeFed solution specifically and concretize this unit of work. Let's keep to discussing ActivityP...

An opportunity for Golang devs to work on a great FOSS project with funding: Bringing Gitea to the Fediverse with ActivityPub support and the ForgeFed protocol…

    • smallcirclesOPM
      3•2 years ago

      Indeed. It is not about federating Git, but federating code forges which increasingly become a whole bundle of different developer services and tools to keep developers locked into a certain centralized platform, if only by FOMO and network effects.

    • @Yujiri
      1•1 year ago

      deleted by creator

      • smallcirclesOPM
        3•2 years ago

        One example (and where the minimum viable product will start) is to federate issue tracking. So that if you want to create an issue in a remote code forge, you can conveniently do that without creating an account and track it from your own forge.

        • @Yujiri
          3•1 year ago

          deleted by creator