Gitlab [2] would is an alternative with similar functionality that's more consistent with the ideology they're trying to promote.
Gitlab [2] would is an alternative with similar functionality that's more consistent with the ideology they're trying to promote.
* the issues
* the wiki
* the community because your local repo is fine,
but nobody knows any other remote than github.Issues - I'm sure these can get recreated, even the discussions. In many cases, people will have those threads in their email.
Wiki - In Github's case, this is also a git repo.
Community - GitHub is rarely the only mechanism used to manage a community. There's likely a domain name and mailing list of some form.
Losing all of the above is certainly painful but I'm trying to point out that it's not irrecoverable. A better question might be how painful would it be to lose that (and the likelihood of losing it) as compared to other options.
Larger project have a domain and a mailinglist but github hosts thousands of small projects which do not exist outside of it, and in theory it should be trivial to keep a second remote and put it in the readme or sync it over git in some way.
I don't see how you lose the community more than with any hosting method. If GitHub were nuked off the face of the earth you have all the contributors in your Git history, just send them a mail with the new location of the repo.
Their goal are being achieved: To spread the word about projects that can create a descentralized internet..
So, can we please give them a break, and the credits for their nice work?
Do you know if any of the open Github competitors store the issues in a decentralized way? Similar to Bugs Everywhere?