Old OCA use with GitHub/Poject Skara

Magnus Ihse Bursie magnus.ihse.bursie at oracle.com
Tue Dec 15 22:00:30 UTC 2020

On 2020-12-14 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.
Sounds like the informational text provided by the bot needs to have a 
fourth case:

"If you have already signed the OCA, but not provided a GitHub user 
name, nor have at least OpenJDK Author status, please <do something to 
notify Dalibor>".

Dalibor, what would the recommended course of action be? Write "/signed" 
as a pull request comment, even if there is no github user name 
associated with the OCA? Modify "/signed" so it takes an argument with 
the email the OCA was registered under, so you can verify?

> 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

More information about the skara-dev mailing list