We want to make it as easy as possible for GitLab users to become GitLab contributors, so we’ve created this guide to help you get started. We have multiple tracks to cater to people of varying interests.
In addition to Open Source Development, there are also Documentation, Translation, and UX Design tracks. Documentation, Translation, and UX Design are all just as important as code, and we'd be happy to welcome your contributions.
We want to create a welcoming environment for everyone who is interested in contributing. Please visit our Code of Conduct page to learn more about our commitment to an open and welcoming environment.
Whether it's fixing bugs, adding new features, helping with reviews, GitLab is a great Open Source community for developers from all backgrounds. Many contributors actually started contributing to GitLab development without being familar with languages like Ruby.
For more information, please visit Contributing to Development page.
Contributing to documentation is a great way to get familar with the GitLab development process and to meet reviewers and other community members. From fixing simple typos to better organizing our documentation, you will find a lot of different areas where you can contribute.
For more information, please visit the Contributing to Documentation page.
GitLab is being translated into more than 35 languages, and this is also driven by wider community members. If you speak another language, you can join more than 1,500 community members who are helping translate GitLab.
For more information, please visit Contributing to Translation page.
In order to help make our product that is easy to use and is built for diverse group of people, we welcome contribution from the wider community. You can help us better understand how you use GitLab and your needs as you work with the GitLab UX team members.
For more information, please visit Contributing to UX Design page.
If you need any help while contributing to GitLab, below are some of the resources that are available.
- Ask questions on the Contributors Gitter Channel.
- Get in touch with Merge Request Coaches. To find a merge request coach, go to the GitLab Team Page and search for "merge request coach". You can also mention Merge Request Coaches by typing
@gitlab-org/coachesin a comment.
- Find reviewers & maintainers of Gitlab projects in our handbook and mention them in a comment.
- If you have feature ideas/questions, you can reach out to product team members.
- For any other questions or feedback, please email