1. Who wants this feature? Personal gitea user / Companies with private gitea / Git hosting website via gitea or others?
2. Why they need this feature?
3. How they want to use this feature?
Maybe you can help them and provide the answers.
> What use case do you have that this would solve?
Issue tracker collaboration. Code collaboration, as you rightly point out, is already taken care of by #git.
As to whether #ActivityPub is anywhere near the right protocol for that, I have my reservations as well. I reckon that #email, #XMPP or #git itself could be used to achieve the same result with less effort.
Having managed projects, and watched a lot of projects be completely mismanaged because many people do not know how to communicate using computers - look at the current uproar surrounding whether people can continue to work with GNU because of RMS (which is why I won't - well, that, and Gnu folks tend to be just absolutely impossible to work with ) I'd caution on "requiring" that.
It's fine to have it as a possibility.
Additionally, while these have become one of the most significant ways to discover software - they're not the only way. I'd also argue that "most significant" is quite a misnomer, considering Apple's "only software from the Apple store," the Steam storefront, and so on - software shops, not code repositories - are how PEOPLE discover things.
Coders may. (I find more via suggestions and seeing what people work on/with.)
Not sure on designers, managers, end users...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!