Sometimes the keepers of the OCA first send you a question about what
has been sent in.
I recall at least one instance when the applicant over-looked that email.
You may want to check your email from around that time.
Meanwhile I can forward this internally to see if that was the case, or
something else ..
-phil.
On 12/20/2016 11:32 AM, Ali Ebrahimi wrote:
Hi Kevin,
I signed Oracle Contributor Agreement form since April and I'm still
waiting to feedback!
On Tue, Dec 20, 2016 at 7:27 PM, Kevin Rushforth <kevin.rushfo...@oracle.com
wrote:
Hi Rony,
See the "How to contribute" page [1] on the OpenJDK site. The first step
is to sign the Oracle Contribute Agreement (OCA) [2]. All code that you
contribute must be your own work and free of IP encumbrances. It becomes
joint property of Oracle, with you retaining your copyright. Code that is
eventually checked into the OpenJFX project is done so under the GPL v2
license with the "Classpath" exception [3]. Oracle may also choose to
license it under other terms (e.g., when producing the Oracle JDK).
To contribute a bug fix, you would indicate your interest in contributing
a patch to a bug, and then work with a Committer in the Project to sponsor
your fix.
The process for getting an enhancement in is a bit more involved, and
requires additional approval since we want to carefully control the API.
You can start by filing an RFE at bugs.java.com [4]. You should also
become familiar with the Java Enhancement Proposal (JEP) [5][6] process,
since any significant new features require a JEP. We require comprehensive
tests as part of any new feature. It is strongly recommended to discuss
your idea on this list first to get some feedback as to whether it is a
feature / API we would consider accepting before you go off and spend much
time prototyping your ideas.
Let me know if there are any questions on any of this.
-- Kevin
