Individual Contributor
Last updated
Last updated
Copyright © 2022 The Linux Foundation®. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks.
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.
