4 ms·
I entirely understand what you are saying, believe me I do. But that is not the way some communities take it. We still see messages like "You could move to Gitl
by trcollinson 8y ago
I entirely understand what you are saying, believe me I do. But that is not the way some communities take it. We still see messages like "You could move to Gitlab but... you know they dropped their production database a couple of years back? Use them at your own risk!"
We learned a lot from the Gitlab outage. It was a simple mistake and not one they will have again, yet people still beat them up for it. I'm not sure the value is there for the company to be super open about their outages and issues.
- calcifer 8y agoOn the contrary, I would trust them quite a bit less, not more, if they had an hours long outage without any explanation.
- repolfx 8y agoPerhaps - but would you even remember it, without the juicy details of what happened? I probably would forget if some service had a few hours downtime a year or two ago, if I didn't know any details to make it stand out from other outages.
- brandon272 8y agoWouldn't they have gotten beaten up over the outage even more had they not offered an explanation? In my experience, customers are often seeking an explanation/post-mortem because their customers are seeking an explanation. If an upstream service goes down for an extended period of time and all you can do is go back to your customers and say, "Your system was down because our provider's system went down for 4 hours. But they won't tell us why.", that not go over well.
- danShumway 8y agoGitlab's response to the the database mistake was a large contributing factor in my decision to move all of my repositories onto their service. Anecdotal, sure, but people like me exist. I don't know if we're in the majority. You'd have to measure somehow and do a cost-benefit analysis I guess.