Contribution Agreements

Individual and corporate contributors are required to execute both

Developer Certificate of Origin (DCO)

All Linux Foundation collaborative projects require contributors to execute a DCO, and ONAP is no exception.  All contributions - patches, test cases, new code, etc. - must be accompanied by the Developer Certificate of Origin at http://developercertificate.org/, certifying that 

1. The contribution was created in whole or in part by you and that you have the right to submit it under the open source license indicated in the file; or
2. The contribution is based upon previous work that, to the best of your knowledge, is covered under an appropriate open source license and you have the right under that license to submit that work with modifications, whether created in whole or in part by you, under the same open source license (unless you are permitted to submit under a different license), as indicated in the file; or
3. The contribution was provided directly to you by some other person who certified (1) or (2) and you have not modified it.
4. You understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information you submit with it, including sign-off) is maintained indefinitely and may be redistributed consistent withthis project or the open source license(s) involved.

Contributor License Agreement (CLA)

The ONAP project requires that contributors are also covered under a CLA in addition to an DCO as per Section 7a of the Technical Charter. More information on CLAs can found HERE

Beginning with the El Alto release signed CLAs for both individual and corporate contributors will be enforced by Gerrit.  Enforcement of this will take place beginning on Monday, July 8, 2019.
In a nutshell, when you go to make a commit if a CLA has not been associated with the gerrit account are using, your commit will be blocked and you will be re-directed to the CLA tool. 

Companies: 3 basic steps are required to enable commits under a Corporate CLA (CCLA) which covers their contributors.

1. The person designated as the company's CLA Manager (the person that will manage the CLA process for ONAP) must log into the LF's CLA tool and add the company to the list
2. Someone from the company with signature authority must log into the LF's CLA tool and sign the CCLA
3. The CLA Manager must add a whitelist of authorized contributors. This can be based upon a domain or by listing specific email addresses.

Corporate contributors using non-work email addresses:  If you are using a gmail or other non-work account to make commits, the CLA Manager for your company can add your non-work address to the email whitelist.

Independent contributors can submit an Individual CLA (ICLA) through the tool as well.

CCLA Corporate Sign-off Status 

as of 4 PM Pacific, July 3rd:

The table below indicates the status of CLA readiness for each company.  Developers form any companies marked "Incomplete" will not be able to commit code once enforcement is enabled. 

Zuzana Blahovska