|
|
| Re: IBM XML Editor Contribution [message #48138 is a reply to message #47546] |
Fri, 08 October 2004 16:04   |
Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
> > What is the best way to integrate a commercial plugin with the IBM XML
> contribution?
>
> I can't tell you what the best way to integrate your code with the
> Eclipse.org code (IBM contribution) is technically - because I haven't
seen
> your code - but I will remind all the newsgroup readers that if you make
any
> changes to the Eclipse.org code (anything from typos in the Javadoc and
> minor bug fixes, all the way to major new functionality within the
existing
> packages), the CPL and EPL licenses require you to open source the
results.
Not necessarily. It depends on what you plan to do with the changes.
|
|
|
| Re: EPL License (was: IBM XML Editor Contribution) [message #48173 is a reply to message #48138] |
Sun, 10 October 2004 21:52 |
 Bjorn Freeman-Benson
Messages: 75
Registered: July 2009 |
Member |
|
|
In a previous post, I had said "if you make any changes to the Eclipse.org
code (anything from typos in the Javadoc and minor bug fixes, all the way to
major new functionality within the existing packages), the CPL and EPL
licenses require you to open source the results". Randy Hudson replied "Not
necessarily. It depends on what you plan to do with the changes."
I would like to clarify that Randy seems correct in that if you make changes
but do _not_ distribute those changes, then there is no requirement to open
source the results. However, if you make changes to any CPL/EPL licensed
code and you _do_ distribute those changes, the license requires you to open
source the results.
============================================================ ================
====
First section 1(b) says that anything which is a change or addition, and is
not a separate module, is a Contribution.
------------------------------------------------------------ ----------------
----
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and
documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i) >>>changes<<< to the Program, and
ii) >>>additions<<< to the Program;
where such changes and/or additions to the Program originate from and are
distributed by that particular Contributor. >>>A Contribution 'originates'
from a Contributor if it was added to the Program by such Contributor itself
or anyone acting on such Contributor's behalf<<<. Contributions do not
include additions to the Program which: (i) are separate modules of software
distributed in conjunction with the Program under their own license
agreement, and (ii) are not derivative works of the Program.
============================================================ ================
====
Section 2.(a) then says that all Contributions are made available subject to
the terms of this Agreement (e.g. EPL).
------------------------------------------------------------ ----------------
----
2. GRANT OF RIGHTS
a) >>>Subject to the terms of this Agreement<<<, each Contributor hereby
grants Recipient a nonexclusive, worldwide, royalty-free copyright license
to reproduce, prepare derivative works of, publicly display, publicly
perform, distribute and sublicense the Contribution of such Contributor, if
any, and such derivative works, in source code and object code form.
============================================================ ================
====
3(b)(iv) then says that if the Contributor ships in object code, that it
must ensure that the source code for the Program is available using some
reasonable mechanism.
------------------------------------------------------------ ----------------
----
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under
its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement: ...
iv) states that >>>source code for the Program is available from such
Contributor<<<, and informs licensees how to obtain it in a reasonable
manner on or through >>>a medium customarily used for software exchange<<<
============================================================ ================
====
So as soon as you make a change it is a derivative work which makes it a
Contribution and the originator a Contributor. Then the Contributor has to
adhere to certain obligations to make the derivative available under the EPL
in source code.
But, hey, I'm not a lawyer, and I don't even play one on TV. I suggest that
if you have questions about license issues the best place to ask them would
be via email to license@eclipse.org
Regards,
Bjorn Freeman-Benson
|
|
|
Powered by
FUDForum. Page generated in 0.05713 seconds
] 
Search
Help
Register
Login
Home
