@andrewnez Consider that gitea contains package registries, and forgejo is the FLOSS fork. It's perfectly possible to build a bunch of these things with a self-hosted forgejo instance.
Which really means that a bunch of things forgejo does should become de facto standards.
There are also things that can be standardized that help here. For example, there are a few competing solutions for platform/language independent package meta information, including dependencies.
Could focus on that, too.