Follow-up docs questions for ActivityPub
The following discussion from !130960 (merged) should be addressed:
-
@aqualls started a discussion: @oelmekki In the spirit of iteration
I'm going to merge this work, so you can submit follow-up MRs as improvements. I'll spin this comment off into a separate issue, and assign it to you, because a few things are missing: -
An issue to provide feedback in. -
An explanation of what the activity_pub
andactivity_pub_project
flags each do. Should users enable both? What happens if they only enable one and forget the other? -
As a UI is developed, it should follow the guidelines in https://docs.gitlab.com/ee/policy/experiment-beta-support.html. -
Add language that says the documentation reflects that the feature is subject to the GitLab Testing Agreement. I'm pretty sure it will be this language but I'll want to check. We can garden it into your next follow-up: Usage of <feature name> is governed by the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/).
Your files are now named:
doc/development/activitypub/index.md
doc/development/activitypub/actor.md
-
Related links
- Related to Add ActivityPub Releases profile and outbox (!127023 - merged) which is the parent of this issue
- Related to https://gitlab.com/oelmekki/gitlab-activitypub-design