Git is a distributed version control system. There doesn’t have to be a single copy of the repo on which everything depends. It’s a choice, and an understandable one, to treat one copy as authoritative, but there’s no reason to deposit if it becomes unavailable. Any copy of it will do.
What GitHub provides that’s hard to do without it is not the repository but the stuff that goes around it: issue tracking, communication tools, discoverability, etc.
So if people take the distributed nature of Git seriously and make sure they all have a local copy of the repo, we won’t lose the repo itself to Nintendo’s actions. But we may lose the tools that make it easy to coordinate work on the repo.
Before we had GitHub and issue trackers we had mailing lists and Usenet groups. Not as convenient, bit they allowed people to coordinate work on open source software without a central, corporately owned point of failure. Maybe we should be looking to the early days of FOSS for ideas about how to make these projects resilient against corporate persecution. Not for the exact tools but for decentralized ways of coordinating collaboration.
There are self hosted github alternatives, like Gitea for example. It takes 10 minutes to set up and it behaves like github/gitlab.
So all to advantages can be kept.
Git is a distributed version control system. There doesn’t have to be a single copy of the repo on which everything depends. It’s a choice, and an understandable one, to treat one copy as authoritative, but there’s no reason to deposit if it becomes unavailable. Any copy of it will do.
What GitHub provides that’s hard to do without it is not the repository but the stuff that goes around it: issue tracking, communication tools, discoverability, etc.
So if people take the distributed nature of Git seriously and make sure they all have a local copy of the repo, we won’t lose the repo itself to Nintendo’s actions. But we may lose the tools that make it easy to coordinate work on the repo.
Before we had GitHub and issue trackers we had mailing lists and Usenet groups. Not as convenient, bit they allowed people to coordinate work on open source software without a central, corporately owned point of failure. Maybe we should be looking to the early days of FOSS for ideas about how to make these projects resilient against corporate persecution. Not for the exact tools but for decentralized ways of coordinating collaboration.
There are self hosted github alternatives, like Gitea for example. It takes 10 minutes to set up and it behaves like github/gitlab. So all to advantages can be kept.