Skip to end of metadata
Go to start of metadata

Individual and corporate contributors are required to execute both

  • A Developer Certificate of Origin (DCO), and
  • A Contributor License Agreement (CLA)

when submitting code for consideration to the ONAP project.

Individuals can agree to the Individual Contributor Acknowledgement.

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, 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.

Corporate Contributor License Agreement (CCLA)

ONAP Project

A project of The Linux Foundation

Software Grant and Corporate Contributor License Agreement ("Agreement") v1.0

Thank you for your interest in the ONAP Project (“ONAP”) of The Linux Foundation (the "Foundation"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the Foundation must have a Contributor License Agreement (CLA) on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of ONAP, the Foundation and its users; it does not change your rights to use your own Contributions for any other purpose.

This version of the Agreement allows an entity (the "Corporation") to submit Contributions to the Foundation, to authorize Contributions submitted by its designated employees to the Foundation, and to grant copyright and patent licenses thereto.

If you have not already done so, please complete and sign, then scan and email a PDF file of this Agreement to the address indicated in the README file within the CLA folder of the ONAP code repository. If necessary, send an original signed Agreement to The Linux Foundation, 1 Letterman Drive, Building D, Suite D4700, San Francisco CA 94129, U.S.A. Please read this document carefully before signing and keep a copy for your records.

Corporation name:                                                                                                      

Corporation address:                                                                                                   



Point of Contact:                                                                                                       



You accept and agree to the following terms and conditions for Your present and future Contributions submitted to the Foundation. In return, the Foundation shall not use Your Contributions in a way that is contrary to the public benefit or inconsistent with its nonprofit status and bylaws in effect at the time of the Contribution. Except for the license granted herein to the Foundation and recipients of software distributed by the Foundation, You reserve all right, title, and interest in and to Your Contributions.

1. Definitions.

"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with the Foundation. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"Contribution" shall mean the code, documentation or other original works of authorship expressly identified in Schedule B, as well as any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to the Foundation for inclusion in, or documentation of, any of the products owned or managed by the Foundation (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Foundation or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Foundation for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to the Foundation and to recipients of software distributed by the Foundation a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

3. Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to the Foundation and to recipients of software distributed by the Foundation a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) were submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

4. You represent that You are legally entitled to grant the above license. You represent further that each employee of the Corporation designated on Schedule A below (or in a subsequent written modification to that Schedule) is authorized to maintain the list of employees of the Corporation who are authorized to submit Contributions on behalf of the Corporation, using the Foundation’s designated system for managing such list.

5. You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others).

6. You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.

7. Should You wish to submit work that is not Your original creation, You may submit it to the Foundation separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".

8. It is your responsibility to notify the Foundation when any change is required to the list of designated employees authorized to submit Contributions on behalf of the Corporation, or to the Corporation's Point of Contact with the Foundation.

Please sign: __________________________________ Date: _______________

Title: __________________________________

Corporation: __________________________________

Individual Contributor Agreement (ICA)

I agree that:

  • My contributions to the Project are made by me as an individual;
  • That my employer, if any, is aware that I am contributing to the Project and has given me permission to contribute to the Project;
  • My contributions to the Project will be made under the license(s) designated by the Project, and accompanied by a Developer Certificate of Origin sign-off; and
  • I have reviewed the Project’s charter and that I will comply with the Project’s charter.

Signed: __________________________________ Date: _______________

Title: __________________________________  Affiliation: __________________________________

  • No labels


  1. Hi, this was raised yesterday at the TSC in Beijing - can we get some guidance on exactly what to fill out and if we send these to our TSC rep per company.

    There is a PTL meet next monday that we can discuss this in - as I understand that commit triggers will be enforced

    I am tracking this for my team in  LOG-495 - Getting issue details... STATUS

  2. Hi there,

    Any updates on guidance regarding the process for submitting the Contribution Agreements? Also, is it only applicable to project committers or to everyone who contributes patches to any projects within ONAP?


    1. Work in progress.  Still.

  3. As far as I know these may only make it to the corporate level – which corporation are you with – can’t tell from your gmail account or your wiki page.

    ONAP acts as one in terms of your LF account.

    When this all started I raised some jira’s to eventually get them signed – I think this is off the radar for now.


    From my perspective you can do 99% of activities with your LF account – you just can’t merge code, create branches or view certain wiki content and some jira capabilities without being a committer on at least one component – but you can push patches at will, contribute to the wiki, newsgroups, help with devops, testing, usability, doc…..


    If you can post patches you are good to go.