Skip to end of metadata
Go to start of metadata

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 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 CharterMore information on the LF's EasyCLA tool 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 EasyCLA Corporate console and add the company to the list
  2. Someone from the company with signature authority must log into the EasyCLA Corporate console 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 13:00 Pacific Aug 1:

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. 

Company CompleteCompany IncompleteTool step completeTool step Pending 


Company CLA ManagerCLA SignedWhitelist type
Amdocssignedemail addr
ARM Limited

AT&T signeddomain
Beijing BOCO

Bell CanadaAlexis de Talhouëtsigneddomain / email 

China MobileShang Yuxiangsignedemail addr
China TelecomSun Qiong


Deutsche Telekomsignedemail addr
ENEAJerome Arpin-Pont signed
Ericsson ABsignedemail addr
Ericsson ESTsigneddomain
FujitsuToshimichi Fukuda


Georgia Tech

H3Cliu wenyusigneddomain
iconectivShiby Parayil

Intel CorporationRajesh Gadiyarsigneddomain / email
IBMsignedemail addr

OAMsigneddomain / email 
Orangesignedemail addr 
Zuzana Blahovska
signedemail addr
QCTsigneddomain / email
Samsungsignedemail addr
Tech Mahindrasignedemail addr
TelstraStephen Hilton

signedemail addr
VerizonEdward Diazsigneddomain
Wind RiverGlenn Seilersignedemail addr
Wiprosignedemail addr
ZTEsignedemail addr

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