Strategy for ActivityPub feature

Product Considerations

There are several aspects which need direction from Product, some of which were discussed on a 25-SEP-2023 sync call GitLab internal only

The feature is comprised of a foundational component, and then feature-specific Actors are implemented on top of it. Currently only the Releases ActivityPub is implemented.

  • Should this be activated for public projects only (cc @tachyons-gitlab) ?
    • Including private projects would add the need to overlay potentially complex authorisation rules across instances
  • Will it be activated on GitLab SaaS?
  • Which group(s) will own and support the features?
  • Do we want to limit the extent of the implementation?
  • Will supporting elements be built? eg: API endpoints, rate limiters