I think a great use case for this Community would be to ask other people to interact with projects on Github/Gitlab on their behalf, and report back the link to new issues or issue comments to the Community.
The URL attached to this post is an example of that, where Pilou created an issue in the Gitea tracker on behalf of Loïc who does not have a Github account for ethical reasons.
(Gitea is still on Github, but they intend to dogfood their own code forge any time soon. The issue Pilou created deals with adding ForgeFed-based federation support to Gitea. See this issue for details. FedeProxy community is trying to speed this up, by arranging funding).
Glad to see we can all count on @pilou@forum.forgefriends.org to proxy our Github issues! Pilou is going to be a busy guy!
I’ve pinned your post for now. Maybe we could also establish a convention of linking to the main bug tracker to make it easier for the proxies. OTOH, I have mixed feelings on this. Proxying the reports as a crutch serves as a co-dependency that enables bug trackers to stay in bad places. Folks can make their own choices of course, but the long-term trend should ideally be to avoid feeding the bad places.
Perhaps one good practice would be for proxied reports to /not/ include a copy of the report. Just a link. Force GH/GL users to go to the source. And perhaps some verbiage to encourage responses going in the more open venue (this community).
