We've hired some great new people recently but as you can see there is still a lot work to do. https://about.gitlab.com/jobs/production-engineer/
Re:GitLab Database Incident – Live Report
by mrmondo on Tuesday January 31, 2017 @10:04PM
(#13537840)
I've just DM'd you in twitter with some PostgreSQL advice ;)
Re:GitLab Database Incident – Live Report
by mrmondo on Wednesday February 01, 2017 @02:10AM
(#13538959)
Note for the person that downvoted my comment: GitLab are fantastic, I'm a big advocate for their product & support. My comment to Sid was in support of helping based on some of the notes I saw in their very transparent report, Sid & I have talked several times in the past & I have quite a bit of PostgreSQL experience - so my comment was a positive one offering support when / if needed, not a negative / piss take if it came off as such.
Re:GitLab Database Incident – Live Report
by sytse on Wednesday February 01, 2017 @06:26AM
(#13539868)
Thanks for that, we'll collaborate on it at the bottom of https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCx...
Re:GitLab Database Incident – Live Report
by Perihelion on Tuesday January 31, 2017 @09:18PM
(#13537606)
There's also this one if anyone is interested in helping out with the DB side of things: https://about.gitlab.com/jobs/specialist/database/
I very much appreciate their forthrightness and the way they conduct their company generally. Having said that, I have the code I work on, related content, and a number of clients on the service.
[edit for additional point]
They need the infrastructure guy they've been looking for sooner than later. I hope there's good progress on that front.