Originally published on strongloop.com
Since the beginning of the LoopBack project, we have been using the Contributor License Agreement (CLA) as the contribution method. Contributors need to sign each CLA for each LoopBack repository they're contributing. To simplify the contribution process and encourage community contributions, we are planning to gradually switch to use Developer Certificate of Origin (DCO) as the contribution method.
What Is Developer Certificate of Origin (DCO)?
As an alternative to CLA, a Developer Ceritifcate of Origin (DCO) is a more lightweight contribution method. According to Wikipedia:
Instead a signed legal contract, a DCO is an affirmation that the source code being submitted originated from the developer, or that the developer has permission to submit the code.
The full text of DCO can be found: https://developercertificate.org/.
Why Are We Switching?
Community contributions are vital to the success of LoopBack. Since DCO simply needs your affirmation that you are the one who is submitting the code, we hope this switch would make the contribution process simpler and thus encourages more contributions from you!
In addition, this change can help us to reduce the infrastructure cost, including the team's time and effort, to maintain the CLA server.
What Does It Mean To You?
Currently, the loopback4-example-shopping is already using DCO.
To sign off the commit, you can:
git commit -s -m "feat: my commit message"
Over the next little while, we'll start the switch for the repositories with the most community contributions, namely loopback-next, loopback.io and loopback-datasource-juggler, then we'll roll it out for the connector repos.
You are more than welcome to contribute on something that you find it relevant and interesting to you. If you're simply looking for items that we want help, you can look for GitHub issues with
help wanted or
good first issue labels.
More questions? Feel free to ask in the #loopback-contributors channel of the LoopBack Slack community.