Considering everyone involved has signed both, what is your concern which would differ if on hg.netbeans.org or any where else? This isn't inherently different if someone added it to hg.netbeans.org today were they an OCA signer; there wasn't any broadcast code freeze. The integrator would have the same role regardless would they not?
Too, for now, this is Emi's repo where the work of the donation was suggested to take place. This isn't yet an official Apache repo. On paragraph 5, that interpretation isn't how patch submission through BZ has worked before nor after Oracle acquisition, so not sure the difference in this scenario to BZ patch submission. Wade On Dec 31, 2016 8:34 PM, "Matthias Bläsing" <[email protected]> wrote: Am Samstag, den 31.12.2016, 20:53 +0200 schrieb Emilian Bold: > Chris did the first pull request on main-silver: > https://github.com/emilianbold/main-silver/pull/1 > > We are still working on polishing it and I will have to manually > commit the > patch under my @netbeans.org ID but this is very nice! I suggest not to do this! There are some very explicit assumptions in the OCA and Apache Contributer Agreement. As the transfer of owner has not happend yet, a commit to the netbeans code base can only be done by oracle or an OCA signee. An OCA signee can only commit code he/she authored (that would be paragraph 5 of the OCA). I know that everybody is excited and it would be nice if the transition would have already happened, but it will take time and getting hectic wont help the process. In this case I suggest to prepare the patch, polish it, clear authorship and save it there. It needs to be cleared when outside code may be merged into the codebase if the committer is not the author and the author has not signed an CA with apache. Greetings Matthias
