how does that help for the long long lists of external dependencies, for the bugtrackers of projects where I'd like to look up if someone else had the same issue and maybe there's a workaround, to view and compare code for older revisions of projects I'm using?
With a ton of projects now hosted on github, github being down is a major dent in my overall productivity even though we _do_ have an internal git server.
For repositories your projects depend on, you can set up a local proxy so you at least have local copies for continuous integration. E.g. PHP's Composer project has _Toran_ and _Satis_ for this: http://tech.m6web.fr/composer-installation-without-github.ht...
doesn't give me easy access to the source, browseable and searchable, I can't link to it when discussing with a colleague via chat, can't browse the docs and the wiki and I can't update them. It's a minor advantage at the cost of running yet another piece in my infrastructure that may die or exhibit problems. We use nexus as a proxy for various repositories and so far I've had nexus down more often than github.
You can host your own Nexus servers, for whatever that's worth, if you were unaware. Again, adding more infrastructure, but it at least solves the "it's down on the internet!" problem.
we are hosting our own nexus servers - but they tend to have issues of their own. Bugs, repositories get broken, storage full, machines down for maintenance and patching, yadda yadda. Githubs track record at being up is better than our nexus track record.
With a ton of projects now hosted on github, github being down is a major dent in my overall productivity even though we _do_ have an internal git server.