4 ms·
Good points. However: Issues - I'm sure these can get recreated, even the discussions. In many cases, people will have those threads in their email. Wiki - I
by amirmc 13y ago
Good points. However:
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.
- phaer 13y agoYes the wiki is a git repo, but the percentage of people who have a (current) checkout of their project wiki is probably below 0.1% of all users. 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.
- foobarian 13y agoYou know, sourceforge was once the place to be for hosting your SVN projects, forums, etc., and nobody batted an eye when they ceased to be the community centroid. Similarly with github, if it shut down or something new and shinier came along the projects would move there before you could say "merge conflict."
- warfangle 13y agoAnd now I dread seeing a sourceforge link on a project site. Absolutely, chest-clenchingly dread.