Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ECA"
m (Bug 471810: [CLA] CLA signing is too complicated) |
|||
| (13 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The Eclipse Foundation has implemented Contributor License Agreements ([http://www.eclipse.org/legal/CLA.php CLA]) to improve its intellectual property (IP) management and workflow. In part, CLAs are a portion of the work required to implement signed-off-by for all contributions coming to Eclipse via Git or Gerrit. | + | The Eclipse Foundation has implemented Contributor License Agreements ([http://www.eclipse.org/legal/CLA.php CLA]) to improve its intellectual property (IP) management and workflow. In part, CLAs are a portion of the work required to implement signed-off-by for all contributions coming to Eclipse via Git or Gerrit. All contributors are required to [http://www.eclipse.org/contribute/cla sign] the CLA before contributing to any Eclipse project they are not a committer on. |
| − | * [[Development Resources/Contributing via Git|Contributing via Git]], a resource for contributors | + | * [http://www.eclipse.org/contribute/cla Sign the CLA] |
| + | * [[Development Resources/Contributing via Git|Contributing via Git]], a resource for contributors | ||
* [[Development Resources/Handling Git Contributions|Handling Git Contributions]], a resource for committers | * [[Development Resources/Handling Git Contributions|Handling Git Contributions]], a resource for committers | ||
| + | |||
| + | If you have any questions about CLAs, please check out the [http://www.eclipse.org/legal/clafaq.php FAQ] first. If that does not answer your questions, please contact [mailto:emo@eclipse.org emo@eclipse.org]. | ||
| + | |||
| + | =Troubleshooting= | ||
| + | |||
| + | '''I have signed the CLA and have signed-off on my commit, but Gerrit is rejecting it.''' | ||
| + | |||
| + | Email address and user name matching is case-sensitive. Make sure that the case you use in your commit credentials matches the case you used when you signed the CLA. | ||
| + | |||
| + | The user name and email address that's in the author field must match (case sensitive) the case in the ''Signed-off-by'' statement. | ||
| + | |||
| + | The ''Signed-off-by'' statement must be in the footer of the commit message. Make sure that there are no blank lines beneath the statement. | ||
| + | |||
| + | Make sure that you aren't pushing more than one commit. The id (SHA) of the commit that's rejected will appear in the output from your failed push. Make sure the id matches that of the commit you think you're pushing. | ||
| + | |||
| + | If that doesn't solve it, open a [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Gerrit bug]. | ||
=Other Links= | =Other Links= | ||
Revision as of 11:24, 18 July 2016
The Eclipse Foundation has implemented Contributor License Agreements (CLA) to improve its intellectual property (IP) management and workflow. In part, CLAs are a portion of the work required to implement signed-off-by for all contributions coming to Eclipse via Git or Gerrit. All contributors are required to sign the CLA before contributing to any Eclipse project they are not a committer on.
- Sign the CLA
- Contributing via Git, a resource for contributors
- Handling Git Contributions, a resource for committers
If you have any questions about CLAs, please check out the FAQ first. If that does not answer your questions, please contact emo@eclipse.org.
Troubleshooting
I have signed the CLA and have signed-off on my commit, but Gerrit is rejecting it.
Email address and user name matching is case-sensitive. Make sure that the case you use in your commit credentials matches the case you used when you signed the CLA.
The user name and email address that's in the author field must match (case sensitive) the case in the Signed-off-by statement.
The Signed-off-by statement must be in the footer of the commit message. Make sure that there are no blank lines beneath the statement.
Make sure that you aren't pushing more than one commit. The id (SHA) of the commit that's rejected will appear in the output from your failed push. Make sure the id matches that of the commit you think you're pushing.
If that doesn't solve it, open a bug.