I am glad you like AMA :) Answer to your question: 1) think about culture you want to build in the company and check it with those you want to hire. 2) understand person motivation, why they are willing to join

Thank you for kind words. GitLab can run on macOS (I do development on it for years without any VM). But Windows is the problem. Most of our dependencies are quite Linux/Unix specific and until those are ported to Windows it's unlikely we can run server code on it.

I think the key to timezone problem in meeting, as well as any attendance problem, is to write everything down. Then no matter if you can't attend because of time difference or for other reason, you can always read it later.

No way. This is one of my favorite features in CI architecture. It stays for long. P.S. Glad you like it :)

We'll catch up. We have a good, feature rich, integrated product. We started as self-hosted product and we have a leading position here now. Next step is making GitLab.com a most popular SAAS for private projects and then we go for public one. Of course, it won't happen in a day. We need to put a lot of efforts to make GitLab.com as stable and performant as we want. But I am quite confident in it.

We love them all. They contribute to product in many ways, from feedback and bug report to actual feature contributions.

We do everything in issues and design is not an exception. When we have idea we create an issue and then someone from UX team comes up with screenshot/mockup of it. Mockups and feedback are posted as comments in the issue. It continues up until approval either from product person or other designer. In the end we have issue with description of what should be done and final screenshot attached. There is also UX channel in Slack where UX team discuss new techniques and approaches.

GitLab started as the weekend hobby. Ruby was my favorite language back in 2011. I wanted to make something useful and practice my skills at the same time. Thanks to Ruby and Rails I was able to release the first version within a month.

Hey, probably certificate issue. Maybe badly copied credentials from GCP. Btw take a look at quick start guide I made for GKE + GitLab.com https://docs.gitlab.com/ce/topics/autodevops/quick_start_guide.html . I tested it several times to confirm it works.

Hi, Our long-term vision is to become the most popular collaboration tool for knowledge workers in any industry. But first, we need to become #1 platform for developers. Which is quite a huge goal considering our scope: from chat and code hosting to CI/CD and monitoring of a deployed applications. Cheers from Kharkiv :)