Community
Participate
Working Groups
I got this note: Dear Eclipse Contributor, Three years ago, you signed an Eclipse Contributor License Agreement (CLA) or an Eclipse Contributor Agreement (ECA) on our website, which has allowed you to submit code contributions to the various Eclipse projects. Thank you! Your CLA or ECA is now expired, and needs to be re-signed before contributing code to Eclipse projects. To re-sign, please follow the link below. https://eclipse.org/legal/ECA.php On behalf of the millions of software developers who use Eclipse, hundreds of Eclipse committers and the staff at the Eclipse Foundation, thank you for helping make Eclipse a great community for open source software development. Best Regards, Mike Milinkovich Executive Director Eclipse Foundation ---- The page it directs me to ends with the sentence: You represent that the information provided below is accurate. But it's the last sentence. There is nothing below. All attempts to follow the instructions lead me to a page that says: Visit the ECA page to learn more. The Eclipse Contributor Agreement that we have on record for you will expire on 2016-07-03 If you've changed employers or your contact information, please invalidate your current ECA and complete the form again. Note that if you invalidate your ECA, it cannot be undone; you will be prompted to sign a new ECA. --- But I've not changed employers so what must I do. In frustration I tried clicking on the big Invalidate ECA button and it says: You have successfuly invalidated your CLA. --- Note that successfuly is spelled wrongly. The problem is that I'm not prompted to sign a new one and all links lead me back to the page I started with. So now I can't commit the Gerrit anymore, and I can't make progress on https://git.eclipse.org/r/#/c/78751/ It's a pretty poor experience for people expecting/hoping to continue contributing to Eclipse.
*** Bug 500826 has been marked as a duplicate of this bug. ***
*** Bug 500813 has been marked as a duplicate of this bug. ***
I managed to get the issue fixed for Ed. If you're blocked to submit some of your work today, please add a comment here and I can try to fix your case manually. The issue is more global than that and still needs to be addressed.
Hi Mickael, Can you also fix the problem for me please?
Same here, most commiters @ obeo are currently stuck with no push rights on gerrit.
(In reply to Laurent Redor from comment #4) > Hi Mickael, > > Can you also fix the problem for me please? Please go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla and you should be able to sign your ECA now. If you don't have push perm to gerrit, please let me know.
(In reply to Cedric Brun from comment #5) > Same here, most commiters @ obeo are currently stuck with no push rights on > gerrit. Let's see if I managed to fix the issue for Laurent. If it's the case, please give me the list of impacted committers email addresses so that I can also fix the issue for them.
(In reply to Mikaël Barbero from comment #6) > (In reply to Laurent Redor from comment #4) > > Hi Mickael, > > > > Can you also fix the problem for me please? > > Please go back to > https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla and you should > be able to sign your ECA now. If you don't have push perm to gerrit, please > let me know. Thanks, I've got a "You successfully submitted the CLA!" message and my CLA is now "green" on bugzilla.
(In reply to Mikaël Barbero from comment #7) > (In reply to Cedric Brun from comment #5) > > Same here, most commiters @ obeo are currently stuck with no push rights on > > gerrit. > > Let's see if I managed to fix the issue for Laurent. If it's the case, > please give me the list of impacted committers email addresses so that I can > also fix the issue for them. So far: cedric.notot@obeo.fr nathalie.lepine@obeo.fr florian.barbin@obeo.fr maxime.porhel@obeo.fr
As I wrote in bug 500813, I have the same problem.
> cedric.notot@obeo.fr > nathalie.lepine@obeo.fr I have no CLA entries on file for them. I can't fix it > florian.barbin@obeo.fr Fixed. > maxime.porhel@obeo.fr It seems that Maxime managed to invalidate its CLA and sign the ECA already.
(In reply to Till Brychcy from comment #10) > As I wrote in bug 500813, I have the same problem. Should be fixed. Go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your CLA
(In reply to Mikaël Barbero from comment #11) > > florian.barbin@obeo.fr > > Fixed. He has to go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla and sign the new ECA.
My CLA is in the same state as comment 0. I could at least push a commit directly to refs/heads/master using the Gerrit pushurl. I pushed from EGit and didn't set Change-Id or Signed-off-by headers.
(In reply to Markus Keller from comment #14) > My CLA is in the same state as comment 0. Should be fixed. Please, go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your ECA
(In reply to Mikaël Barbero from comment #12) > (In reply to Till Brychcy from comment #10) > > As I wrote in bug 500813, I have the same problem. > > Should be fixed. Go back to > https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign > your CLA Worked, thanks.
I have the same issue, as I reported earlier this morning in https://bugs.eclipse.org/bugs/show_bug.cgi?id=500826 but I was at least able to push a updated patch to gerrit.
(In reply to Xavier Coulon from comment #17) > I have the same issue, as I reported earlier this morning in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=500826 but I was at least able > to push a updated patch to gerrit. Should be fixed. Please, go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your ECA
Hello Mikaël, Thanks for the prompt answer! I confirm that I was actually able to renew my CLA.
Does this still require manual fixing for each individual? If so, please do the same for my account, too.
(In reply to Stephan Herrmann from comment #20) > Does this still require manual fixing for each individual? If so, please do > the same for my account, too. Me too.
(In reply to Stephan Herrmann from comment #20) > Does this still require manual fixing for each individual? If so, please do > the same for my account, too. Should be fixed. Please, go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your ECA.
(In reply to Dawid Pakula from comment #21) > (In reply to Stephan Herrmann from comment #20) > > Does this still require manual fixing for each individual? If so, please do > > the same for my account, too. > > Me too. Not sure if the workaround fixed your problem as well. Please, go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your ECA. If it does not work, please report back.
Me too. Although I still can push content, I'm marked with out-of-date ECA and can't find a way to sign it.
"You successfully submitted the CLA!" great, except: shouldn't it read "ECA"?
(In reply to Mickael Istria from comment #24) > Me too. Although I still can push content, I'm marked with out-of-date ECA > and can't find a way to sign it. Should be fixed. Please, go back to https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign your ECA.
I can't create patches for gerrit.
(In reply to Snjezana Peco from comment #27) > I can't create patches for gerrit. It seems like you have a different problem. What is the error message you are getting?
(In reply to Frederic Gurr from comment #28) > (In reply to Snjezana Peco from comment #27) > > I can't create patches for gerrit. > > It seems like you have a different problem. What is the error message you > are getting? remote: Reviewing commit: 974701fa remote: Authored by: Snjezana Peco <snjezana.peco@redhat.com> remote: remote: The author is not a committer on the project. remote: error: The author does not have a current Contributor License Agreement (CLA) on file. remote: If there are multiple commits, please ensure that each author has a CLA remote: remote: The author has "signed-off" on the contribution. remote: Please see http://wiki.eclipse.org/CLA To ssh://speco@git.eclipse.org:29418/sourceediting/webtools.sourceediting ! [remote rejected] HEAD -> refs/for/master (A Contributor License Agreement is required.) error: failed to push some refs to 'ssh://speco@git.eclipse.org:29418/sourceediting/webtools.sourceediting' https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla Visit the ECA page to learn more. The Eclipse Contributor Agreement that we have on record for you will expire on 2019-09-01 If you've changed employers or your contact information, please invalidate your current ECA and complete the form again. Note that if you invalidate your ECA, it cannot be undone; you will be prompted to sign a new ECA.
(In reply to Frederic Gurr from comment #23) > Not sure if the workaround fixed your problem as well. Please, go back to > https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla to re-sign > your ECA. If it does not work, please report back. Not work, I see "The Eclipse Contributor Agreement that we have on record for you will expire on 2016-08-21" and "Invalidate ECA" button. When I click Invalidate I see flash message with success but still cannot sign ECA. I had signed CLA before.
I have the same problem as mentioned in comment #0. Can you please fix my account too?
Ick, mea culpa. This is a nasty old bug in some of our old code. Patch submitted, pending.
(In reply to Denis Roy from comment #32) > Ick, mea culpa. This is a nasty old bug in some of our old code. > > Patch submitted, pending. I am encountering this problem too. What is the status of the patch? Thanks!
Hi all, I've the same problem. What can I do? Many thanks.
Hi all, I have the same problem. Any update of the patch status? Thank you very much
We patched this a couple of weeks ago. You may be among the few that may need to invalidate the CLA and sign the new ECA. Have you tried doing that?
Thank you Danis, I've invalidated the old CLA and submit a new one. Now it works.
I see the message that says my ECA will expire 2016-07-29. When I click the invalidate ECA button I get the following message: We were unable to invalidate the CLA we have on record. (LDAP-02) I can't seem to invalidate or sign a new ECA/CLA. Can you help? Thanks.
(In reply to Mark Joy from comment #38) > I see the message that says my ECA will expire 2016-07-29. When I click the > invalidate ECA button I get the following message: > > We were unable to invalidate the CLA we have on record. (LDAP-02) > > I can't seem to invalidate or sign a new ECA/CLA. Can you help? > Thanks. This should be fixed by now, can you confirm it's working for you now?
(In reply to Christopher Guindon from comment #39) > (In reply to Mark Joy from comment #38) > > I see the message that says my ECA will expire 2016-07-29. When I click the > > invalidate ECA button I get the following message: > > > > We were unable to invalidate the CLA we have on record. (LDAP-02) > > > > I can't seem to invalidate or sign a new ECA/CLA. Can you help? > > Thanks. > > This should be fixed by now, can you confirm it's working for you now? Yes, this is working now. I was able to sign a new ECA/CLA. Thanks.
(In reply to Mark Joy from comment #40) > (In reply to Christopher Guindon from comment #39) > > (In reply to Mark Joy from comment #38) > > > I see the message that says my ECA will expire 2016-07-29. When I click the > > > invalidate ECA button I get the following message: > > > > > > We were unable to invalidate the CLA we have on record. (LDAP-02) > > > > > > I can't seem to invalidate or sign a new ECA/CLA. Can you help? > > > Thanks. > > > > This should be fixed by now, can you confirm it's working for you now? > > Yes, this is working now. I was able to sign a new ECA/CLA. Thanks. Thanks. Closing this bug!
