Come on, GitHub is used for serious work for several big companies. One hour downtime is an eternity, I'm quite happy with reporting 10 minute downtimes, as most of my workflow involves github, every step of the development process (ticketing system, dev vm's, CI server, capistrano, etc...) all at some point connect with GitHub.
It's quite odd how so may Git advocates relentlessly stress the importance of decentralized source control, yet they turn around and centralize so heavily on GitHub (including source control).
I agree that it's an important tool and should be discussed.
But...if you're a big company, who's doing serious work, then take advantage of the fact that git is a DVCS and have something as a failover measure. GitHub is great and has lots of great features, but there's nothing stopping people from having a mirror synced without all the sugar but to keep productivity going.
Comments
Come on, GitHub is used for serious work for several big companies. One hour downtime is an eternity, I'm quite happy with reporting 10 minute downtimes, as most of my workflow involves github, every step of the development process (ticketing system, dev vm's, CI server, capistrano, etc...) all at some point connect with GitHub.
It's quite odd how so may Git advocates relentlessly stress the importance of decentralized source control, yet they turn around and centralize so heavily on GitHub (including source control).
I agree that it's an important tool and should be discussed.
But...if you're a big company, who's doing serious work, then take advantage of the fact that git is a DVCS and have something as a failover measure. GitHub is great and has lots of great features, but there's nothing stopping people from having a mirror synced without all the sugar but to keep productivity going.