Due to git's distributed nature, there should be very few people who are not able to work on their code.
Oh the irony! Actually I bet many developers are sitting on their hands when they can't access github.
I don't want to dump on github. It has been a great driver of open-source software. But by making itself a single-point-of-... so much, it kind of defeats the purpose of git sometimes.
Ideally we'd be able to download not just the repo but all the meta-info; issues, comments, pull requests, etc.
That would be true if enterprises had their own local git repositories, and if employees pushed against those local git repositories. But this is not what happens, when enterprises use github, employees directly push to github.
Continuous integration tools directly pull from github.
When github is down, all exchange of patches between employes essentially halts, as does continuous integration and testing.
Of course, this is not the fault of git.
This is the fault of people keeping using centralized servers, instead of setting up and using their own local servers.
The same goes for email (gmail anybody? Really???)
The Internet is meant to be a decentralized, peer-to-peer, meshed network. Not a centralized, star network!!!
Comments
Due to git's distributed nature, there should be very few people who are not able to work on their code.
Also, it's Sunday, so very few employees are expected to be working today.
Oh the irony! Actually I bet many developers are sitting on their hands when they can't access github.
I don't want to dump on github. It has been a great driver of open-source software. But by making itself a single-point-of-... so much, it kind of defeats the purpose of git sometimes.
Ideally we'd be able to download not just the repo but all the meta-info; issues, comments, pull requests, etc.
That would be true if enterprises had their own local git repositories, and if employees pushed against those local git repositories. But this is not what happens, when enterprises use github, employees directly push to github.
Continuous integration tools directly pull from github.
When github is down, all exchange of patches between employes essentially halts, as does continuous integration and testing.
Of course, this is not the fault of git.
This is the fault of people keeping using centralized servers, instead of setting up and using their own local servers.
The same goes for email (gmail anybody? Really???)
The Internet is meant to be a decentralized, peer-to-peer, meshed network. Not a centralized, star network!!!
You can just pull from someone's local copy, a git checkout is just like a remote (bare) repository that happens to have a tree.
If you're an enterprise you're using github's on-premise appliance and aren't affected at all.
In a pinch, you can always pull from a coworker's local repository.