A corporate contributor is one who contributes code on behalf of their employer (and not on their own behalf). If you are contributing code on your own behalf, please see the Individual Contributor workflow.
Upon creating a pull request in GitHub or merge request in GitLab or submitting changed code in Gerrit, EasyCLA will check whether the contributor is authorized under a signed CLA for that project. If they are not, and if they are contributing on behalf of their employer, then they will need to be authorized under a signed Corporate CLA (CCLA):
If their company has not yet signed a CCLA, then the contributor can start the workflow for the signing process.
If the contributor has not yet been added to the authorized contributors list by their company's CLA Manager, then the contributor can submit a request to their CLA Manager to be added.
If the CCLA has been signed and the contributor is on the authorized contributors list, then the contributor will need to confirm their association with the company, and then will be able to proceed.
In GitHub, go to the repository that is linked to your project.
Make a code change and create a pull request.
EasyCLA checks the CLA status of all committers involved in that pull request.
EasyCLA displays a cross or a check mark beside the name of each contributor involved in that pull request based on their CLA status.
A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.
If the Auto Enable Acknowledgement workflow is enabled, the CLA check is passed. For more information, refer Auto Enable Acknowledgement Workflow.
5. Click Authorize LF-Engineering. (Subsequent contributions will not require authorization.)
Result: The CLA Contributor Console appears in a new tab.
6. Click Proceed as a Corporate Contributor.
7. On Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.
Note:
If your company is not in the list, you can add the company as described in If your company is not in the list.
8. You will need to complete one of the following workflows:
Auto enable acknowledgement workflow allows corporate contributors to bypass an additional step of logging into the Corporate CLA Console twice. This workflow helps the corporate contributors to seamlessly contribute to the project.
The main aim of this workflow is to eliminate multiple login into Corporate console by corporate contributors. Corporate contributors should login once into Corporate console and then they will be free to contribute to the projects with out worrying to login into corporate console multiple times.
The following diagram shows the new auto enable acknowledgement workflow for corporate contributors:
To auto enable acknowledgement workflow for Corporate Contributors, perform the following steps:
1.Login into Corporate CLA.
2.Search for the project and click EasyCLA.
3.Enable the Auto ECLA button.
3.Once the Auto ECLA button is enabled, the CLA Manager will add your name to the approval list. For more information, refer Add Contributors.
4.When the CLA Manager adds your name, you can successfully submit your changes to the project in GitHub without logging into Corporate Console to get an additional acknowledgement that your a contributor to the project.
This additional step is eliminated by implementing the Auto Enable Acknowledgement workflow.
In Gerrit, clone a repository under the Gerrit instance into your local machine.
Make a change and push the code to your Gerrit repository.
A warning link that you need to sign a CLA appears if CLA is not signed for the project:
4. Navigate to the Gerrit instance of your project. For example, if you are contributing to the ONAP project, navigate to https://gerrit.onap.org
5. Sign in using your LF 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. Click Corporate CLA, and then click the Please review the agreement link.
9. Click Proceed To Corporate Authorization.
Result: You are redirected to the EasyCLA Corporate Console. Sign in with your LF SSO account if prompted.
10. On Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.
11. You will need to complete one of the following workflows:
In GitLab, clone the repository you want to contribute to.
Make changes, commit change and create merge request.
EasyCLA checks the CLA status of all committers involved in that pull request.
EasyCLA displays a cross or a check mark beside the name of each contributor involved in that pull request based on their CLA status.
A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.
5. Click Authorize (Subsequent contributions will not require authorization.).
Result: The CLA Contributor Console appears in a new tab.
6. Click Proceed as a Corporate Contributor.
7. On the Select Organization window, type your company's name in the field, select it from the drop-down list, and click Proceed.
Note:
If your company is not in the list, you can add the company as described in If your company is not in the list.
8. You will need to complete one of the following workflows:
Click +Click Here next to the Organization not listed?
2. Provide organization website URL, and organization name in the respective fields. Note: If the website URL is already associated with an organization, the organization name appears in the Organization Name field, and you cannot edit the name.
3. Click Next.
4. Click an answer: Are you authorized to be a CLA Manager for your organization?
Yes: Follow the procedure, and click Proceed to coordinate the CCLA signing process.
No: Provide name and email address of the person who is authorized to be the CLA Manager from your company for this project, and click Submit Request. If you do not know who should be the CLA Manager from your company for this project, you should consult with your management or legal department to confirm.
Note: After the authorized person signs CLA, and adds you to the approved list, you must complete your company acknowledgement before you can contribute.
If your company has not yet signed a CLA, the No Signed CLA Found window appears after selecting your company.
Click an answer: Are you authorized to be a CLA Manager for your organization?
Yes — By clicking Yes, you will become the initial CLA Manager after the CCLA is signed.
No — By clicking No, you will enter the details of someone else who will become the initial CLA Manager.
Click Proceed on the window that appears.
Note: If you don't have a username (LF SSO Account) associated with The Linux Foundation, you will be redirected to the LF SSO Account creation page.
2. Click Proceed again.
3. You will be redirected to the corporate console to coordinate the CCLA signing process.
Important: After the CCLA is signed, you will be the initial CLA Manager, but by default you will not also be an authorized contributor. In order to contribute to the project, you must then add yourself to the approved list, and complete the company acknowledgement.
Complete the form, and click Submit Request. If you don't know the email address of the person who should become the CLA Manager of your company, then (unless you just created the company record) you can click the Contact Company Admin link, which may let you reach out to your company's LFX administrative contact if your company has set someone up with this role.
Click Exit EasyCLA. You can contribute after your company signs the project's CCLA, and the CLA Manager adds you to the approved list.
Important: You will receive an email after the CLA Manager adds you to the approved list. After you are added to the approved list, you must complete your company acknowledgement before you can contribute to the project.
If your company has signed a CCLA, but you have not yet been added to the approved list, the Request Authorization to Contribute window appears that shows the CLA Manager(s) for your company.
Select one or more CLA Managers from the drop-down list whom you want to request to add you to the authorized list.
3. Click Exit EasyCLA.
Important: You will receive an email after the CLA Manager adds you to the approved list. After you are added to the approved list, you must complete your company acknowledgement before you can contribute to the project.
After the CCLA is signed and the CLA Manager adds you to the approved list, you must re-select your company association before you can contribute code under that company's signed CCLA.
Navigate to the GitHub PR page or GitLab merge request page.
Click Not Covered, and then click Proceed as a Corporate Contributor.
On the Select Organization window, select your company, and click Proceed.
Navigate to the Gerrit instance of your project, and re-complete the procedure by following step 4 through step 10 as described above under Gerrit section to complete company acknowledgement.
A window appears confirming your association with the company. Click Exit EasyCLA, and start contributing.
Important: If the status on Git command line still shows "No contributor agreement" when you push the code change, you need to navigate to the Gerrit window, sign out, sign in again, and then push the code.
For certain projects, in addition to being authorized under your company's signed CCLA, you may also be required to individually sign an ICLA on your own behalf.
Click Proceed.
Follow the instructions in DocuSign, sign the ICLA, and click FINISH.
GitHub/GitLab Contributors: Navigate to the GitHub/GitLab page. Wait a few seconds for the CLA status to be updated or refresh the page.
Gerrit Contributors: If the status on Git command line still shows "No contributor agreement" when you push the code change, you need to navigate to the Gerrit window, sign out, sign in again, and then push the code.
4. Click or Please click here to be authorized.
4. Click or Not Covered.
An Identify CLA Manager window appears.
2. Click Request Authorization.
A window appears confirming your association with the company. Click Exit EasyCLA, and you will be redirected back to the GitHub or GitLab page where the CLA status will be updated. If it does not immediately update, please wait a moment and then refresh the page.
\
If this is the case for your project, then after your CLA Manager adds you to the approved list, and after you complete your company acknowledgement, then the following screen appears:
On CLA Ready For Signature window, click SIGN CLA.
A Contributor is someone who contributes either on behalf of a company, or individually on their own behalf.
If contributing on behalf of their company: the contributor will sign a Corporate Contributor License (CCLA).
If contributing on their own behalf: the Contributor will sign an Individual Contributor License Agreement (ICLA).
Important: You should not submit a contribution under an ICLA if that contribution is done on behalf of your company. Instead, you should contribute under a Corporate CLA signed by your company. If you are uncertain whether you should be contributing under a CCLA or an ICLA, you should consult your employer's legal department to discuss.
An individual contributor is one who contributes code on their own behalf (and not on behalf of an employer). If you are contributing code on behalf of your employer, see the Corporate Contributor workflow.
Upon creating a pull request in GitHub or GitLab or submitting changed code in Gerrit, EasyCLA will check whether the contributor is authorized under a signed CLA for that project. If they are not, and if they are contributing on their own behalf, then they must sign an ICLA.
In GitHub, clone the repository want to contribute to Or click the pencil icon next to a file of the repository to edit; it will clone the repository under your username.
Make a change and create a pull request.
EasyCLA checks the CLA status of all committers involved in that pull request. EasyCLA displays a cross or a check mark beside the name of each contributor who is involved in that pull request based on their CLA status.
A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require this authorization.)
The CLA Contributor Console appears and shows the CLA group for your project.
Note: If the project is not configured to use ICLAs, then Proceed as an Individual Contributor is inactive. In this case, individuals would not be able to contribute on their own behalf.
6. After the CLA Ready For Signature window appears, click SIGN CLA.
DocuSign presents the ICLA document for your signature.
7. Select the check box and click CONTINUE. Follow the instructions in the DocuSign document, fill in the indicated fields, sign it, and click FINISH.
Result:
You will receive an email from The Linux Foundation, informing you that you have signed the ICLA.
You are redirected to GitHub. Wait a few seconds or refresh the page for the EasyCLA status to be updated. A check mark appears next to your branch.
8. Click Merge pull request and confirm the merge.
In Gerrit, clone a repository under the Gerrit instance into your local machine.
Make a change and push the code to your Gerrit repository.
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 the OPNFV project, navigate to https://gerrit.opnfv.org
5. Sign in using your LF 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. Click Proceed To Individual Authorization.
10. Sign in if you are prompted, and you will be redirected to the Contributor Console.
11. After CLA preparation is completed, click Sign CLA.
DocuSign presents the ICLA document for your signature.
12. Select the check box and click CONTINUE. Follow the instructions in the DocuSign document, fill in the indicated fields, sign it, and click FINISH.
Result:
A message appears informing you that you have signed the ICLA.
You will also receive an email from The Linux Foundation, informing you that you have signed the ICLA.
13. Navigate to the Gerrit project, and start contributing.
Important: If the status on Git command line still shows "No contributor agreement" when you push the code change, you need to navigate to the Gerrit window, sign out, sign in again, and then push the code.
In GitLab, clone the repository you want to contribute to.
Make a changes, commit change and create a merge request.
EasyCLA checks the CLA status of all committers involved in that commit. EasyCLA displays a cross or a check mark beside the name of each contributor who is involved in that commit based on their CLA status.
A cross next to a contributor's name means the EasyCLA check has failed, because the contributor is not authorized under a signed CLA.
4. Click Authorize LF-Engineering. (Subsequent contributions will not require this authorization.)
The CLA Contributor Console appears and shows the CLA group for your project.
Note: If the project is not configured to use ICLAs, then Proceed as an Individual Contributor is inactive. In this case, individuals would not be able to contribute on their own behalf.
6. After the CLA Ready For Signature window appears, click SIGN CLA.
DocuSign presents the ICLA document for your signature.
7. Select the checkbox and click CONTINUE. Follow the instructions in the DocuSign document, fill in the indicated fields, sign it, and click FINISH.
Result:
You will receive an email from The Linux Foundation, informing you that you have signed the ICLA.
You are redirected to GitLab. Wait a few seconds or refresh the page for the EasyCLA status to be updated. A check mark appears next to your branch.
8. Ask someone with write access to the repository to merge your commit request.
3. Click or Please click here to be authorized.
5. Click Proceed as an Individual Contributor.
You can download the PDF document by clicking the link from the email. You will be re-directed to the Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
You can download the PDF document by clicking the link from the email. You will be redirected to the Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
3. Click or Not Covered.
5. Click Proceed as an Individual Contributor.
You can download the PDF document by clicking the link from the email. You will be re-directed to the Linux Foundation's website. If the download doesn't start automatically, click Proceed to Download.
