We are so glad you are interested in contributing to CARTO! We'd like to make contributing as easy as possible. That said, there are a few guidelines.
At CARTO, we manage a lot of open source projects, and we are required to have agreements with everyone who contributes. This is the easiest way for you to give us permission to use your contributions. When you sign a Contributor License Agreement (CLA), you’re giving us a license, but you still own the copyright — so you retain the right to modify your code and use it in other projects.
We require that you (or the organization you're working for) complete and sign a Contributor License Agreement unless you are contributing an Obvious Fix.
Email us at email@example.com to request a Contributor License Agreement. Include your full name and provide us a bit of detail about why you are contributing. Are you working on a personal project? Are you working on behalf of an employer or client? This detail will help us ensure we handle everything properly.
Once you've signed the CLA:
We regularly review contributions and will get back to you if we have any suggestions or concerns.
See below for more information about CLAs, licenses, and the Obvious Fix rule.
A contributor licensing agreement (CLA) must be filled out by every contributor to a CARTO-managed open source project.
The CLA makes everyone’s rights clear:
The CLA is beneficial to our contributors and users because:
CARTO's contribution policy is aimed at encouraging broad participation from our community and minimizing risks to CARTO and our community due to inappropriate contributions of the intellectual property of others.
As a general standard, CARTO requires every contributor to fill out a Contributor License Agreement (“CLA”), either individually or on behalf of a corporate entity.
HOWEVER, very small contributions (such as fixing spelling errors), where the content change is small enough to not be considered intellectual property, can be submitted by a contributor as a patch, without a CLA. If you submit an Obvious Fix without first signing a contributor license agreement, then you are agreeing that your submission is not independently copyrightable. The purpose of this exception is to lower the barrier for new contributors to make contributions while retaining the integrity of the project and our community.
Any committer may commit fixes without first signing a CLA for obvious typos, grammar mistakes, and formatting problems wherever they may be.
Whenever you invoke the Obvious Fix Rule, please say so in your commit message. For example:
commit 375t3248vkdd912b0cf9c1d1e99b13 Author: javier <firstname.lastname@example.org> Date: Tue Jul 24 12:15:03 2013 -0500 Fix typo in install file docs. Obvious fix.
An obvious fix is a pull request that does not contain creative work. We rely on your judgment to determine what is “obvious”; if you’re not sure, just ask by sending an email to: email@example.com.
As a rule of thumb, changes are obvious fixes if they do not introduce any new functionality or creative thinking. As long as the change does not affect functionality, some likely examples include the following:
Things that would still require signing a CLA before submitting would likely include stuff like the following:
Please fill out the below form and we'll be in touch real soon.