News for hackers. Stuff that matters.
Re:GitLab Database Incident – Live Report by omouse on Wednesday February 01, 2017 @12:06PM (#13542475)
On the contrary, it comes off as very professional. All other companies would hide this, they would show off a very cleaned up post-mortem and say "problem solved" and that's it. Ok so what does that mean, does it mean the process will change for the future or that they just fixed it for today?

This is also an awesome advert to see how they work remotely all together and I'm sure they're hiring for DevOps people now ;)

Re:GitLab Database Incident – Live Report by throwaway91111 on Wednesday February 01, 2017 @03:07PM (#13544550)
Naming individuals is not professional. Even allowing it with permission does not set a good standard for operation.
Re:GitLab Database Incident – Live Report by riralk on Saturday February 04, 2017 @02:28AM (#13566080)
I agree the transparency was probably appreciated by most users. I also think the human factor should be considered not just the technical aspect. Here's my take on the issue... https://forgetfulprogrammer.wordpress.com/2017/02/04/key-lea...