All the cool kids post code to Github these days, and many open source projects have adopted Github as their main tool for managing the development of their projects. Just recently it was announced that Python is moving their main repository to Github. For the last few hours (nearly 6 hours), Github has been struggling with a major network outage. This was also just noted by The Register. Hopefully Github's engineers will get to the bottom of it. At least with Git, even if Github is down, developers can still work with their code and commit changes to their local repositories and then push later when service is restored. This is but one example of the pitfalls of cloud hosting, though I daresay that Github's uptime is much better than most IT departments' own servers.
Last time similar things happened (Mar 2015), it was blamed on China.
[NOTE: The above was submitted shortly after 1:00 AM (UTC) on 2016-01-28.
GitHub has a status page which, as of this writing, is reporting: "Everything operating normally."
GitHub also posts a list of recent status messages. -Ed.]
(Score: 3, Informative) by tibman on Thursday January 28 2016, @03:22PM
Github isn't git, it just uses it. Git isn't like svn or tfs or other version control systems. Every git client is also a server. If github (or your own central git server) goes down then you can still push code to each other (or anywhere). People can even push code straight to your local machine. Think of it like your webbrowser is also a webserver and you have your own local copy of the internet. If the real internet went down you'd just use your local copy. To keep it updated you could pull from other content/website creators directly. Or if you made changes you could push those directly to other people. Having a central place only makes it easier for everyone to collaborate.
SN won't survive on lurkers alone. Write comments.