As an individual contributor, you are contributing code on your own behalf (not on behalf of an employer). You create a pull request in GitHub or submit changed code in Gerrit to inform reviewers about the changes. During the process, your CLA is verified, and you must sign a CLA if you have not already signed, before you can contribute to GitHub or Gerrit.
1. Navigate to the GitHub repository that is linked to the project for your organization.
2. Make a change and send a pull request.
EasyCLA checks your CLA status. It marks a cross or a tick beside your name based on your CLA status.
A cross next to your contributor name means the CLA check failed.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)
The CLA Contributor Console appears and shows the CLA group for your project. The CLA types display:
5. Click Individual and then click OPEN CLA.
DocuSign presents the agreement that you must sign. The ICLA is not tied to any employer you may have, so enter your @personal address in the E-Mail field.
6. Follow the instructions in the DocuSign document, sign it, and click FINISH.
You receive an email from The Linux Foundation, informing you that you have signed the CLA.
You are redirected to GitHub. Wait a few seconds for the CLA status to update. A tick appears next to your branch.
7. Click Merge pull request and confirm the merge.
1. In Gerrit, clone a repository under the Gerrit instance into your local machine.
2. Make a change and push the code to your Gerrit repository.
3. A warning link that you need to sign a CLA appears:
4. Navigate to the Gerrit instance of your project. For example, if you are contributing to OPNFV project, navigate to https://gerrit.opnfv.org​
5. Sign in using your Single Sign-On (SSO) account.
6. Navigate to Settings— the gear icon on the upper right corner, and click Agreements from the menu on the left:
7. Click New Contributor Agreement.
8. Select Individual CLA (ICLA), and click Please review the agreement.
9. Sign in to EasyCLA if you are prompted.
10. Click OPEN CLA on the dialog that appears: DocuSign presents the agreement that you must sign. The Individual CLA is not tied to any employer you may have, so enter your @personal address in the EMail field.
11. Follow the instructions in the DocuSign document, sign it, and click FINISH.
You are redirected to Gerrit. Wait a few seconds for the CLA status to update.
3. Click or Please click here to be authorized.
​
You can download the PDF document by clicking the link form the email. You will be redirected to Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
​​ ​​
As a corporate (employee) contributor, you are contributing code on company's behalf. When Corporate CLA is signed for the project, you confirm your association with the company during your first pull request or change submit. Your subsequent contributions will neither require association confirmations nor will they be gated by CLA check.
1. In GitHub, go to the repository that is linked to the project for your organization.
2. Make a change and send a pull request.
EasyCLA checks your CLA status. It marks a cross or a tick beside your name based on your CLA status.
A cross next to your contributor name means the CLA check failed.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)
5. The CLA Contributor Console appears and shows the CLA group for your project.
6. Select Company. Note: To contribute to this project, you must be added to an approved list by the CLA manager under a signed Contributor License Agreement. You are contributing on behalf of your work for a company.
7. Continue:
1. In Gerrit, clone a repository under the Gerrit instance into your local machine.
2. Make a change and push the code to your Gerrit repository.
3. A warning link that you need to sign a CLA appears:
4. Navigate to the Gerrit instance of your project. For example, if you are contributing to OPNFV project, navigate to https://gerrit.opnfv.org​
5. Sign in using your Single Sign-On (SSO) account.
6. Navigate to Settings— the gear icon on the upper right corner, and click Agreements from the menu on the left:
7. Click New Contributor Agreement.
8. Select Corporate CLA, and click Please review the agreement.
9. Sign in to EasyCLA if you are prompted.
10. Continue:
11. After you complete signing the CLA, navigate to gerrit window, sign out from gerrit, and sign in again for the CLA status to be updated.
This message appears if you are added to the approved list, and your CLA doesn't require you to sign ICLA. If the CLA is configured for you to sign ICLA, you will be redirected to sign an Individual CLA, as shown in step 5 of sign ICLA.
1. Read the Confirmation of Association statement and select the checkbox.
2. Click CONTINUE.
A dialog appears and informs you: You are done!
3. Click RETURN TO REPO.
You are redirected to GitHub. Wait a few seconds for the CLA status to update or refresh the page.
You must be added to the approved list under a signed CCLA before you can contribute to the project.
To contact your CLA manager to add you to the approved list:
1. Click CONTACT under Contact the CLA Manager to be approved under their signed Corporate CLA.
2. Select an option, and complete the form.
3. Click SEND. A message appears informing you that the e-mail is sent successfully.
You will receive an email notification if the CLA manager approves or rejects your request to be approved as a corporate contributor for the company.
If your company has not signed CLA, Verify Your Permission window appears. To proceed:
Click an answer: Are You a CLA Manager?
YES— You will be redirected to the CLA Corporate Console to sign a CLA.
Complete the form and click SEND.
The CCLA manager signs a Corporate CLA and adds you to the approved list.
If you don't find your company's name in the list:
Click COMPANY NOT IN LIST? CLICK HERE.
The Verify Your Permission of Access dialog appears.
Click an answer: Are You a CLA Manager?
YES— You will be redirected to the CLA Corporate Console to add your company to a project.
Complete the form and click SEND.
The CCLA manager signs a Corporate CLA and adds you to the approved list.
As a contributor, you must sign CLA document before you can contribute to a repository. EasyCLA lets you sign CLAs from within a pull request. After you sign a CLA or sign a confirmation of association with your company, the status of your pull request is updated and you can contribute.
You can contribute on behalf of a company or contribute individually by doing one or both of the following tasks:
Important: You should not submit a contribution under an Individual CLA if that contribution is done using time and/or material resources belonging to your company. Instead, you should contribute it under a Corporate CLA signed by your company.
3. Click or Please click here to be authorized. Note: The Authorize Linux Foundation: EasyCLA dialog appears.
​​
​​ ​​
NO— A Request Access form appears. Continue to next step.
NO— A Request Access form appears. Continue to next step.
​. You write code for your employer and contribute this code to a project on your employer's behalf.
​. You are contributing code on your own behalf (code that you write on your own time, and not for an employer or using your employer’s facilities or equipment).
Gerrit contributors, see .