For a while now I've been dual hosting my projects on both Github and Codeberg and adding a note in the README's [1] explaining the situation. I donate to Codeberg and run my own self-hosted forgejo runners for actions, and maintain much of my testing on both platforms.
I push to Github and then an Action mirrors the code to Codeberg automatically.
I'd fully switch over except practically everybody is on Github and nobody is on Codeberg, and I've had more outages with Codeberg than Github over the past year.
It really feels like there could be some good tooling in this area to make working through multiple Forge's easier and not force things to be centralized so much. Hopefully more projects moving out of Github makes it easier and gets more people contributing elsewhere.
What do you find lacking in tooling in that regard?
I don't think there is all that much friction in distributing git, it's one of the easiest tools to have multiple remotes on. The auxiliary tooling is all open source too, so not much in the way of hosting your own, or for hosted platforms offering the services.
The social aspect of the hosted platforms is unlikely to ever be distributed because that is basically githubs only differentiation.
I think OP means multiplying n repos by m hosts and you get nXm assets out of sync , and lots of manual labor keeping track
A managed update service could work to replicate and then raise an error during conflicts . Call it “agentic” and you might get $75m