I reached a point where I need to write code to better understand how all this could work. And since I’m very new to all this the chances are very high that all of it will be thrown away once I have a better understanding. I’m leaning towards:
- Representing issues using the GItLab import/export format
- Storing them in a dedicated branch of the code repository of the software project
- Announcing issues in the same way PeerTube does with videos using the permalink of a commit as the object instead of the permalink of a video
- Copying pasting ActivityPub code from activitystreams2