Sep 2, 2019 - Brendan O'Leary    

Why I'm so excited to go to GitLab Commit

Spoiler alert: It's that I'm going to get to see GitLabbers who I don't work with

This blog post is Unfiltered

It is probably no surprise that I'm a little biased when it comes to GitLab. Heck, I've even used it to make breakfast and organize home improvement ideas. But the thing is - my excitement around the first GitLab Commit event has very little to do with GitLab the product or the company. I'm most excited to get a chance to come together as GitLabbers.

We recently made it very clear that "GitLabber" is not a term that means a person who is paid by GitLab - for that we say team-member. And that's because of one of GitLab's key advantages as a tool and company is our open core model and the over 2000 people who have directly contributed code to GitLab itself. Those are a LOT more GitLabbers than we could ever hope to hire at GitLab, Inc.

But the wider community has so much more influence in shaping GitLab the product and the company than that. As someone who really, truly values DevOps as a transformative practice - it's incredibly humbling to get a chance to "open source" the best way to do DevOps.

And honestly, that's the part of GitLab Commit in Brooklyn next month that I'm most excited about. The professionals coming to talk about how they've used DevOps to benefit their organizations are an incredible, diverse set of folks. And they are from many industries - Delta Airlines, Goldman Sachs, MITRE, GNOME. And the list goes on.

Hearing those speakers is going to be enlightening - the topics cover the entire span of DevOps. Topics like developer efficiency, code quality, CI/CD, and innersourcing will help everyone attending understand how to level up their DevOps journey. On top of that, the attendees will participate in the conference AND the future of GitLab.

Software has eaten the world, and the folks coming to New York represent the best and brightest minds in this new world. And I can't wait to learn from them. Probably people are expecting to learn about GitLab when they are there. And sure, there's going to be a lot of time for that (support engineers, product team-members, etc.). But I think that the GitLabbers we will all learn the most from will be those who don't work for GitLab.

DISCLAIMER: This blog is intended for user-generated content submitted by the GitLab team. The views and opinions represented in this blog are personal to the author of each respective blog post and do not represent the views or opinions of GitLab unless explicitly stated. All content provided on this blog is for informational purposes only. Neither GitLab nor any of the individual blog contributors ("Contributors") make any representations as to the accuracy or completeness of any information on this site. Neither GitLab nor any Contributors will be liable for any errors or omissions in this information or any losses, injuries, or damages from the display or use of this information. Comments are welcome, and in fact, encouraged. However, GitLab reserves the right to edit or delete any comments submitted to this blog without notice should GitLab determine them to i) be spam or questionable spam; ii) include profanity; iii) include language or concepts that could be deemed offensive, hate speech, credible threats, or direct attacks on an individual or group; or iv) are in any other way a violation of GitLab's Website Terms of Use. GitLab is not responsible for the content in comments. This policy is subject to change at any time.