Old OCA use with GitHub/Poject Skara

[Dalibor Topic]

Hi Johannes,

you've done the right thing by reaching out to the list ;)

I'll send a verification e-mail to the e-mail provided on the OCA, and 
once you reply, your GitHub account will be marked as verified.

cheers,
dalibor topic

On 14.12.2020 17:11, Johannes Kuhn wrote:
> Back in Nov 21, 2019 I signed the OCA, but I did not supply a username.
> 
> Now I tried to create a draft PR[1], but the bridgekeeper bot doesn't 
> recognize me as OCA signer.
> 
> It supplied instructions for the following cases:
> * Not already signed the OCA: Not applicable, as I already signed it. [2]
> * If I'm already an Author, Committer or Reviewer: Not applicable, as I 
> did not reach that yet.
> * If the OCA was signed by my employer: Not applicable, as I did sign it 
> myself.
> 
> Anyway, I left a /signed comment, and now it tells me to wait until my 
> OCA is processed (it already is).
> So in all, I'm now in a limbo - what is the right thing to do now?
> 
> - Johannes
> 
> [1]: https://github.com/openjdk/jdk/pull/1767
> [2]: 
> https://www.oracle.com/technical-resources/oracle-contributor-agreement.html 
> 
> 

-- 
<http://www.oracle.com> Dalibor Topic
Consulting Product Manager
Phone: +494089091214 <tel:+494089091214>, Mobile: +491737185961
<tel:+491737185961>, Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRB 246209
Geschäftsführer: Ralf Herrmann