We've just created and published our Strategy document to make our choices clear as they relate to our strategic objectives.
Here we would like to share our thoughts about these issues and what we’re planning to do to make things better with GitLab.
We've recently detailed our policy and commitment to open source. We need to think in the interests of the project, while tending to the realities of running a business to support it.
This time last year, from January until March 2015, GitLab participated in the winter 2015 batch of Y Combinator.
At GitLab we believe you shouldn’t wait for something to be perfect: Release what you have and do it on a schedule.
This is a start in describing the workflow that we've established over the past year at GitLab.
We're announcing a move from doing the majority of our development work internally, to almost exclusively working in public issue trackers on GitLab.com.
In GitLab we have one invisible hero every month, when we have our release on the 22nd of every month which we have never missed!
I started working with GitLab 2 months ago and it has been quite an interesting experience to work remotely with a team that's spread out in the world.
View the GitLab remote working manifesto and the multitude of life-balance benefits it allows our employees to enjoy. Learn more here!
In this post, we look at two instances where we at GitLab dropped the ball, and how we used these errors to learn and improve. Learn more here!
In this post, we'll show you why we're changingthe the GitLab 7.7 user interface, how we did it and what the end result is.