I don't think git should be the infrastructure of collaboration. It's good for long-lived artifacts, but isn't good for discussion, for rights management, ...

fossil (https://fossil-scm.org/home/doc/trunk/www/index.wiki) is of course better, but if git must remain, I believe the base infrastructure should be the mailing list. Patches, branches and releases can live inside a mailing list, it is naturally built for discussion with rights, and is a natural queue for third-party tools. I wish we moved away from centralized forges and started to use augmented development clients with the mailing list as the sole communication vector.