Key takeaways of the discussion with @arthurlogilab:
- There is a confusion between referencing an issue (i.e. mentionning an issue in another issue) and federating an issue which essentially means copying the issue and keeping this copy up to date
- Merging two users may not be implemented as expected in GitHub (see successors)
- Getting a root token on a forge to deploy fedeproxy is a requirement that is too strong: sysadmins will not trust fedeproxy with a root token until it has a good track record of not containing bugs that may leak or loose data. It is simpler to assume a root token is available for the initial implementation. But the next step is to make it so fedeproxy provides the user with the desired experience even when the token is an application/user token. For instance it will not be able to create users and a workaround is needed to represent comments that are authors by users that exist on the remote forge but not on the local forge.
- The separation of responsibility between the two communications channel (ActivityPub & git) must be articulated: it is unclear.