Jerome.Arpin-Pont@enea.comIndividual 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, 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 with this 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 a DCO as per Section 7a of the Technical Charter for both Corporate and individual contributors. A CLA defines the terms under which content (such as source code or documentation) can be contributed to the project.  Enforcement of a having signed CLA to commit code began via the LFX EasyCLA tool in 2019 with the El Alto release of ONAP.  LFX EasyCLA ensures that code can only be committed if a CLA has been associated with the account are using. If there is no CLA on file your commit will be held and you will be re-directed to LFX EasyCLA to either be added to a Corporate CLA (CCLA) or an Individual CLA (ICLA) as appropriate for your situation. Unlike a DCO which is required for every commit, a CLA only needs to be completed with your first commit. 

A Corporate CLA (CCLA) is used when an you are contributing code on behalf of your employer

The details on setting up a CCLAs can be found here, but there are three basic steps are required to enable someone can commit coder under a CCLA.

  • An individual designated as the company's CLA Manager (the person that will manage the CLA process for ONAP) must log into the EasyCLA Corporate console and register their company as contributing to ONAP.  
  • Once the company is registered, the company's CLA Signatory (someone the authority to sign legal documents) must log into the EasyCLA Corporate console and electronically sign the CCLA.
  • Once the CLA is signed, the CLA Manager must add a list of authorized contributors to the tool. This can be done either as automatic authorization based upon a domain name, or by listing individual email addresses for specifically authorizes employees. Employees using a non-work account for their contributions must be added the list by their CLA Manager.

An Individual CLA (ICLA) are used when you are contributing code on your own behalf  and not on behalf of an employer.

ICLAs can be authorized via Gerrit. The instructions to do so are here


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


  4. Hi,

    has anyone experienced issues with Corporate Contributor Agreement? For me nothing happens after I confirm association with my company and click continue (it only shows loading circle next to the button).

  5. Several others have experienced this.  I suggest entering a ticket at the LF help desk: