The commenter mentioned a decentralized Git system that manages issues and patches in addition to the source code and doesn't require a central server. The replication can happen in the background. Moreover, it can work over Tor, which allows NAT traversal and thus an ability to collaborate without having an external IP or a dedicated server.

Greg Wilson - Sometimes I write, sometimes I teach, sometimes I ...

Q for research friends: have you started planning what to do if the US gov't suddenly restricts access to GitHub? Could happen in several ways, e.g., Microsoft has to filter DEI content to stay eligible for federal contracts or a "nothing Ukrainian" rule, but the mechanism doesn't matter: what does it that it's no longer impossible. Yes, you have a clone of your repo, but not of your issues, and how will you reconnect with contributors? If you have a plan, please share a link - thanks.

Later: please note that I'm not looking for "have you tried backup tool X?" but rather for people who have made or are making (and testing out) concrete plans for what they will do, in what order, to avoid a repeat of our near-miss with SourceForge almost going offline back in the day.

Pamphile Roy - Senior Software Engineer at Bitpanda

It's a recurring discussion in the Scientific Python ecosystem. I have been looking at a few decentralized options recently. Because why move to something like GitLab or else if it's to have the same sort of issues. Radicle.xyz looks promising.