If your workflow involves services that integrate with GitHub, you should have a plan for when GitHub is not available. You've got your source code elsewhere, you should have docs and procedures for running the tests in your own dev environments and for utilizing whatever staging/deploy process you prefer without GitHub as an intermediary.
I continue to post comments like that because while I love GitHub, watching the community put all their eggs in GitHub's basket, especially when GitHub lives on top of a tool designed to avoid SPoFs, is concerning.
100%. GitHub is amazing. GitHub is a wonderful tool. GitHub is also just a service cooked up by a handful of jokers who got enough funding to make it happen, and they do a reasonable job of keeping it running most of the time. I wish them all the best, and yet making my own company's infrastructure reliant on it is not something I'm comfortable with. Sometimes they're going to blow it, and that's ok. If them blowing it means my business is affected, I'm the dummy.
While I agree with the general gist of your comment, GitHub was entirely self-funded up until about a year ago or so. they didn't "get" funding, they made real money and reinvested it and grew.
Fine, bootstrapping jokers are my favorite kind of jokers. No offense intended. My point is it's just a small company with no SLA, express or implied. It could have been anybody with the same great idea, and just because they had a great idea doesn't make them automatically reliable enough to pin your infrastructure on.
No? The fact that GitHub is based on a distributed tool is a large part of what makes it so awesome. I can take advantage of the sweet social/collaborative elements of GitHub without locking myself to a central server. If the lower-level they used weren't so open/distributed, I doubt GitHub would have taken off like it has.
Comments
If your workflow involves services that integrate with GitHub, you should have a plan for when GitHub is not available. You've got your source code elsewhere, you should have docs and procedures for running the tests in your own dev environments and for utilizing whatever staging/deploy process you prefer without GitHub as an intermediary.
I continue to post comments like that because while I love GitHub, watching the community put all their eggs in GitHub's basket, especially when GitHub lives on top of a tool designed to avoid SPoFs, is concerning.
100%. GitHub is amazing. GitHub is a wonderful tool. GitHub is also just a service cooked up by a handful of jokers who got enough funding to make it happen, and they do a reasonable job of keeping it running most of the time. I wish them all the best, and yet making my own company's infrastructure reliant on it is not something I'm comfortable with. Sometimes they're going to blow it, and that's ok. If them blowing it means my business is affected, I'm the dummy.
While I agree with the general gist of your comment, GitHub was entirely self-funded up until about a year ago or so. they didn't "get" funding, they made real money and reinvested it and grew.
Fine, bootstrapping jokers are my favorite kind of jokers. No offense intended. My point is it's just a small company with no SLA, express or implied. It could have been anybody with the same great idea, and just because they had a great idea doesn't make them automatically reliable enough to pin your infrastructure on.
You're saying it as if it were a bad thing.
No? The fact that GitHub is based on a distributed tool is a large part of what makes it so awesome. I can take advantage of the sweet social/collaborative elements of GitHub without locking myself to a central server. If the lower-level they used weren't so open/distributed, I doubt GitHub would have taken off like it has.