Blog Open Source GitLab Code Contributor: Vitaliy Klachkov
Published on: August 8, 2018
3 min read

GitLab Code Contributor: Vitaliy Klachkov

Core Team member Vitaliy Klachkov shares how he started contributing to GitLab.


Welcome to our new blog series featuring code contributors from the GitLab community! This blog will highlight the wonderful contributions made by GitLab community members and will hopefully inspire others to contribute to GitLab. For the first blog post, we are happy to welcome Vitaliy “blackst0ne” Klachkov, who has been chosen as a release MVP three times!

How long have you been contributing to GitLab?

I've been contributing since August 2016.

Why and how did you decide to contribute to GitLab?

I read a news article about a new GitLab release and I didn’t even know what GitLab was back then. There was also a discussion on an example of a Rails-based project with a good codebase, and people suggested taking a look at GitLab.

I was intrigued and decided to take a closer look at GitLab. I actually found room for improvement in the codebase so I started pushing a few merge requests (MRs). I received responses within 1-2 days and I was very impressed. With some of the other communities, I’m used to waiting weeks for feedback.

So, I kept submitting more merge requests and so far, I have 227 merged MRs. I’m proud that I’m one of the top 50 contributors among 2000+ GitLab code contributors that include GitLab employees.

Which areas of the GitLab product do you contribute to?

Mostly it has been backend changes, but many of my MRs touched the frontend as well. I spent my time bringing popular features (e.g. squash and merge to CE, mermaid support, switch markdown engine to CommonMark, customizable branch name from issues, etc.), fixing technical debts (e.g. migrate all spinach specs to rspec), upgrading GitLab to Rails 5.0, and many other improvements.

Can you tell us what you do professionally?

I am a full-stack web developer at GEOPHYSTECH LLC. The company is focused on seismology, earthquakes, and everything related to earthquake hazards.

What do you like to do when you're not working?

I’m a big fan of sports or anything that keeps my body moving, such as running, swimming, snowboarding, table tennis, volleyball, ice-blading, football, CrossFit workout, etc.

I also enjoy chess, reading books/articles, and UX-related things. I’ve been collaborating with GitLab’s UX team.

What advice do you have for others who may be interested in contributing to GitLab?

Contributing to GitLab is easy. If you want the experience of being a part of a popular open source project, you are more than welcome to join the GitLab community! You can also ping me on Twitter if you have any questions or need any help as you get started.

Do you have anything else you’d like to share?

GitLab has some nice swag! I’ve gotten some great ones for my release MVPs.

Interested in learning how you can contribute?

A good place to start would be the Contributing to GitLab page, where you can learn how you can contribute to GitLab code, documentation, and translation.

Note: This post is part of a series featuring people who contribute to GitLab.

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

Find out which plan works best for your team

Learn about pricing

Learn about what GitLab can do for your team

Talk to an expert