in reply to daniel:// stenberg://

Fair enough. But do consider that if you switch to Codeberg, it does use Forgejo as the backend, so if you need to switch away from Codeberg to a self-hosted Forgejo instance, the build CIs for Forgejo that you would have built on Codeberg should still work, so you wouldn't have to scrap all the build CIs again, you should be able to reuse those again.

(I'm not too familiar with the inner workings on Forgejo, so correct me if I'm wrong)

Of course, that depends on whether you want to migrate cURL to Codeberg. We (as the community) would love to have you on there, but if not, that's okay.

Crunch, I'd even be okay if you set up an official mirror on Codeberg that mirrors the GitHub repo. At least then the root source code isn't nuked if GitHub goes down.

But that's all up to you. I trust that you will do what's in the best interest for the FOSS community. :blobfoxfloofhappy:

in reply to Rachael Ava πŸ’πŸ»β€β™€οΈ

@RachaelAva1024 No significant project lacks redundancy like this. It's just inherent to how git works. Everyone working on a project has a full copy of its history and all you need to know yours matches someone else's (modulo sha1 attacks) is the hash of the last commit in common.
in reply to daniel:// stenberg://

I doubt that it will be *lots* of additional work, but I see your point. Disclaimer: I am part of a team running free-to-use federated infra structure for Java User Groups, so I well know what the actual costs are. Maybe then codeberg will be interesting for you, which imposes *no* work on the developer, but still is perfectly democratic and open?
⇧