All contributions to GitLab are subject to the Developer Certificate of Origin (DCO), or the Corporate or Individual Contributor License Agreement (CLA), depending on where you're contributing and on whose behalf.
Learn more about our commitment to open source stewardship.
You can make AI-generated contributions to GitLab, including documentation and code, provided you follow these guidelines.
The GitLab mission is to make it so that everyone can contribute. We believe and envision that every company will need to become an AI company to stay competitive. Additionally, we believe that AI functionality will lead to major improvements in GitLab and our customers’ workflows. AI-generated contributions can assist us in achieving our mission and vision, and are welcome, provided that these contributions are in line with these guidelines.
These guidelines may change based on what we learn over time – we will continue to review and iterate as necessary to reflect the best practices in responsible development.
By contributing to GitLab, you are deemed to have accepted the agreement (DCO, or Corporate or Individual CLA) applicable to your contribution.
To enter into an overarching Corporate CLA that covers all contributions made on behalf of a corporate contributor, reach out to cla_managers@gitlab.com
.
A record of contributions to GitLab and their respective contributors is maintained indefinitely in the Git commit history, in recognition of our commitment to contributor recognition.
However, in line with the practice of many other open source software projects, and The Linux Foundation’s guidance, GitLab asks that contributor copyright notices are not added to contributions. To date there are approximately 3611 unique contributors to the GitLab project - maintaining copyright notices for all these contributors places a significant burden on maintainers and downstream distributors for little tangible benefit, and in almost all countries a copyright notice is not required for a contributor to retain ownership of their contribution.
Yes. You retain all rights in, and remain the owner of, your contributions. By accepting the terms of the GitLab CLA or DCO, you are granting GitLab broad permissions to use your contribution, but doing so does not undermine your right to use your contributions for any other purpose.
No. The permissions you grant to GitLab are perpetual and cannot be withdrawn.
The Individual CLA is used when a contribution is made by an individual person, on their own behalf. The Corporate CLA is used when a contribution is made on behalf of an organization. If you are in doubt of which CLA is appropriate for a contribution, we recommend discussing this with your employer.
During preparation of a Corporate CLA, GitLab will create a group for the organization on gitlab.com under https://gitlab.com/gitlab-corporate-cla. This group will be used to manage authorized contributors on behalf of the organization. A designated number of individuals from the organization will be able to manage members of their group. This group will not be public, and as such will only be visible to members of the group.
The Legal and Corporate Affairs team (behind cla_managers@gitlab.com
) remain the DRI for this process. They are supported as necessary by the Contributor Success Team.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Cookie Policy
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, enabling you to securely log into the site, filling in forms, or using the customer checkout. GitLab processes any personal data collected through these cookies on the basis of our legitimate interest.
These cookies enable helpful but non-essential website functions that improve your website experience. By recognizing you when you return to our website, they may, for example, allow us to personalize our content for you or remember your preferences. If you do not allow these cookies then some or all of these services may not function properly. GitLab processes any personal data collected through these cookies on the basis of your consent
These cookies allow us and our third-party service providers to recognize and count the number of visitors on our websites and to see how visitors move around our websites when they are using it. This helps us improve our products and ensures that users can easily find what they need on our websites. These cookies usually generate aggregate statistics that are not associated with an individual. To the extent any personal data is collected through these cookies, GitLab processes that data on the basis of your consent.
These cookies enable different advertising related functions. They may allow us to record information about your visit to our websites, such as pages visited, links followed, and videos viewed so we can make our websites and the advertising displayed on it more relevant to your interests. They may be set through our website by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertisements on other websites. GitLab processes any personal data collected through these cookies on the basis of your consent.