All,
Konstantin's answer is exactly correct. But I would like to add a
little more context to this.
In the past Glassfish and the other Oracle-led projects required
contributors to sign the Oracle Contributor Agreement, which gave
Oracle joint ownership of any outside contributions. So Oracle
owned 100% of the copyright in the projects. That is not how the
IP flows work for Eclipse projects.
The Eclipse Foundation uses a model called "symmetrical
inboud/outbound licensing", which means that all contributions are
(a) still owned by the contributors, (b) contributed under the
project license (e.g. EPL-2.0), and (c) made available to
consumers under that same project license. This means that no
single party --- not Oracle, not the Eclipse Foundation itself ---
gets any particular rights in the projects. Once EE4J gets going
and other people and organizations start to contribute, no one ---
not Oracle, not the Eclipse Foundation itself --- will have the
ability to unilaterally re-license the projects.
We like this model because it puts all of the contributors on a
level footing.
HTH
On 2017-10-30 1:38 PM, Konstantin Komissarchik wrote:
Under Eclipse Development Process (EDP), all contributors retain
their copyright, but agree to license the contribution under EPL.
So, the initial contribution would be copyrighted by Oracle. Any
non-Oracle contribution that are made to the project once it’s
started will have that person’s or company’s copyright.
Thanks,
- Konstantin
Will Oracle still be holding the copyrights
after being an Eclipse project?
How does this fit with contributors' effort?
|