Home / Companies / GitLab / Blog / Post Details
Content Deep Dive

We're switching to a DCO for source code contributions

Blog post from GitLab

Post Details
Company
Date Published
Author
Jamie Hurewitz
Word Count
435
Company Posts That Month
11
Language
English
Hacker News Points
-
Post removed?
No
Summary

GitLab has decided to replace its Contributor License Agreement (CLA) with a Developer's Certificate of Origin (DCO) to encourage more contributions from the open-source community. This change, prompted by feedback from Debian developers, addresses the common criticism that CLAs are overly restrictive and deter potential contributors due to their legal complexity. By adopting the DCO, GitLab aims to provide contributors with greater flexibility and control over their contributions, aligning with the needs of large open-source projects that wish to maintain independence from vendors. The move has been welcomed by figures in the open-source community, including representatives from GNOME and Debian, who believe it will foster more contributions and protect the intellectual property rights of developers.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.