Hi Sharon,
The summary is I'm not sure if I need to add notice.html to the
Triquetrum builds using Tycho. I've cc'd the incubation list because
this came up recently there and have included the thread for your reference.
A big part of my job at Berkeley is dealing with licenses for Ptolemy
II, so I'm very interested in seeing how Eclipse handles licenses and
also in getting it right, hence my overly detailed questions.
The details:
I started looking into this because in the Triquetrum Initial CQ
approval (dev.eclipse.org/ipzilla/show_bug.cgi?id=10434), you wrote:
We would ask the project to ensure it has in place all required legal bits as
described here [1] in case that has not been done.
[1] https://eclipse.org/legal/guidetolegaldoc.php
<https://eclipse.org/legal/guidetolegaldoc.php>
guidetolegaldoc.php says:
*The Location:*
The SUA usually appears in the root directory of Eclipse builds as the
file named "notice.html". A copy of the Project's primary license(s)
must appear in the same location as the SUA. In most cases this will
be the Eclipse Public License alone.
*Note:* The appropriate SUA and a copy of any referenced license
*must* be located in the root directory of any Eclipse.org distributed
build (typically distributed as a ZIP file). Any web page that makes
builds available *must *have a link to the appropriate SUA with
appropriate wording.
/The SUA Checklist/
* Every build distribution has the standard SUA in the root as
"notice.html"
* Every build distribution has a copy of the primary license(s) in
the root, e.g., "epl-v10.html"
I'm not sure what a build distribution is. Are all distributions build
distributions or is it only a distribution that includes source files?
Searching the website yields a link to
https://www.eclipse.org/legal/guidetolegaldoc2.php, which is seems to be
an older version of https://eclipse.org/legal/guidetolegaldoc.php, the
older version should probably be removed.
The older version says:
Every build distribution, such as a zip or tar file, must contain a
Eclipse Foundation Software User Agreement
<https://www.eclipse.org/legal/epl/notice.html> (known as the "SUA")
in the root directory of the distribution in HTML format in a file
named "notice.html".
I decided to look at the Eclipse download and it does not seem to have
notice.html at the top level
I downloaded eclipse-rcp-neon-R-macosx-cocoa-x86_64.tar.gz from
https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/neon/R/eclipse-rcp-neon-R-macosx-cocoa-x86_64.tar.gz
and it seems like notice.html is not included at the top level.
bash-3.2$ cd /Applications/Eclipse\ 5.app
bash-3.2$ find . -name "notice*"
./Contents/Eclipse/configuration/org.eclipse.osgi/301/0/.cp/doc/notices.html
./Contents/Eclipse/features/org.eclipse.oomph.p2_1.4.0.v20160606-0856/rootfiles/notice.html
./Contents/Eclipse/features/org.eclipse.oomph.setup.core_1.4.0.v20160530-1355/rootfiles/notice.html
./Contents/Eclipse/features/org.eclipse.oomph.setup_1.4.0.v20160606-0856/rootfiles/notice.html
I would expect to find notice.html at /Applications/Eclipse\
5.app/Contents/Eclipse/notice.html. Is it missing?
I'm using Tycho to create installers, and I did find a way add files to
the root directory at
https://wiki.eclipse.org/Tycho/Demo_Projects/RCP_Application
Should I be adding notice.html as a top level file?
BTW - there is an open bug about this at 'Revisit the requirement about
"notices" in "each build distribution"'
https://bugs.eclipse.org/bugs/show_bug.cgi?id=480073
It could be that I should add bugs for some of these issues, but I
thought a little discussion could help first.
Thanks,
_Christopher
On 7/18/16 6:49 PM, Jeen Broekstra wrote:
On 19/07/16 09:58, David Smiley wrote:
I very much sympathize with your feelings on the notice being
misleading; I was
told to do it this way as well.
Thanks David. I'll take that as a "it's required" so I'll just include
it. If the question comes up from users we can always explain.
RE your second question, the format; my project, Spatial4j, graduated
from
incubation with a notice in Markdown format. Feel free to take it:
https://github.com/locationtech/spatial4j/blob/master/notice.md
Excellent, thanks!
Regards,
Jeen
David Smiley <[email protected]> wrote:
Jeen,
I very much sympathize with your feelings on the notice being
misleading; I was told to do it this way as well.
RE your second question, the format; my project, Spatial4j, graduated
from incubation with a notice in Markdown format. Feel free to take it:
https://github.com/locationtech/spatial4j/blob/master/notice.md
~ David
On Mon, Jul 18, 2016 at 4:57 PM Jeen Broekstra
<[email protected] <mailto:[email protected]>> wrote:
I am struggling a bit with applying the requirements as set out in
https://eclipse.org/legal/guidetolegaldoc.php to the technology.rdf4j
project.
First of all, the guide says that including the standard SUA in the
project root
as "notice.html" is required.
However, the standard SUA is very much EPL-based and seems written
from the
perspective of the main Eclipse IDE project. I appreciate that it says
"unless
otherwise indicated", and that I can indicate (by adding an about file
and a
license file) that we operate on a different license (EDL, in our case).
Nevertheless, including it in the project root in this fashion is bound to
confuse potential users, and likely to cause the (incorrect)
perception that
rdf4j is EPL-licensed, or dual-licensed.
Should I just accept that confusion and include it as-is, or can I
leave it out?
As the guide says, the main purpose of the SUA is merely to say that
"unless
otherwise indicated EPL applies", and since EPL _doesn't_ apply to our
project,
it seems pointless to include it.
Second question: the guide emphasizes in several places that the
included legal
files (the about file, the license, and the SUA) must be included as
html files.
Is this really a hard requirement? The reason I ask is that plain text (or
Markdown) would make viewing these documents on GitHub a lot easier.
Thanks,
Jeen
--
Christopher Brooks, PMP University of California
Academic Program Manager & Software Engineer US Mail: 337 Cory Hall
CHESS/iCyPhy/Ptolemy/TerraSwarm Berkeley, CA 94720-1774
[email protected], 707.332.0670 (Office: 545Q Cory)
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
