Using gerrithub as committer first time

[iloveeclipse]

I've pushed my first commit to gerrithub (https://eclipse.gerrithub.io/c/eclipse-egit/egit/+/1211160) and I wonder if my account is properly configured.
I'm supposed to have committer rights on both jgit and egit, however I see following on push in Eclipse:

commit 02df587: Reviewing commit: 02df5872
commit 02df587: Authored by: Andrey Loskutov <my name@gmx.de>
commit 02df587: 
commit 02df587: Reviewing commit: 02df5872dba2c889af1bee3c8362501b5dd4811c
commit 02df587: Authored by: Andrey Loskutov <my name@gmx.de>
commit 02df587: Eclipse user 'aloskutov'(author) is not a committer on the project.
commit 02df587: Eclipse user 'aloskutov'(author) has a current Eclipse Contributor Agreement (ECA) on file.
commit 02df587: Eclipse user 'aloskutov'(committer) is not a committer on the project.
commit 02df587: Eclipse user 'aloskutov'(committer) has a current Eclipse Contributor Agreement (ECA) on file.
commit 02df587: 
commit 02df587: This commit passes Eclipse validation.

SUCCESS

  https://eclipse.gerrithub.io/c/eclipse-egit/egit/+/1211160 Make ClipboardPropertyTester configurable and disabled by default [NEW]

I've followed steps in https://github.com/eclipse-egit/egit/wiki/Contributor-Guide#using-gerrit.
Here how my settings look like on gerrit hub:

Do I miss something?

[tomaswolf]

This is a known problem. Also happens for me and for every other EGit or JGit committer. Just ignore it, Gerrit still knows and treats you as a committer, and as long as the Eclipse Foundation's ECA checker can find your ECA, all is fine.

We looked at this shortly after the migration of EGit and JGit to Github, and IIRC my strong suspicion at the time was that the Eclipse Foundation's ECA checker was never updated to account for the move of these projects. At the old git.eclipse.org, the projects were named "egit/egit" and "jgit/jgit", while here and at GerritHub, they are "eclipse-egit/egit" and "eclipse-jgit/jgit", and the ECA checker cannot relate these paths to the EF's EGit and JGit projects. The Gerrit plug-in calling the EF's ECA checker API passes the Gerrit project paths to identify the project, and those have changed.

(And completely unrelated: that the two projects are in different organizations is another mistake that should not have happened since it prevents us from moving issues between the projects.)