Re: [eclipse.org-planning-council] Re: consuming orbit bundles

[Christian Damus <cdamus@xxxxxxxxxx>]

Hi, Bjorn,

Are you raising bugs for the Orbit about.html
problems?  Also, the Software User Agreement (license.html) template
in the Eclipse website's legal corner (http://www.eclipse.org/legal/epl/notice.php)
has a section that references a number of licenses as potential inclusions
in the feature:

--- snip ---
THE ABOUTS, FEATURE LICENSES, AND FEATURE
UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES
OR TERMS AND CONDITIONS. SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE
(BUT ARE NOT LIMITED TO):

Common Public License Version 1.0 (available
at http://www.eclipse.org/legal/cpl-v10.html)
Apache Software License 1.1 (available
at http://www.apache.org/licenses/LICENSE)
Apache Software License 2.0 (available
at http://www.apache.org/licenses/LICENSE-2.0)
IBM Public License 1.0 (available at
http://oss.software.ibm.com/developerworks/opensource/license10.html)
Metro Link Public License 1.00 (available
at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)
Mozilla Public License Version 1.1 (available
at http://www.mozilla.org/MPL/MPL-1.1.html)

IT IS YOUR OBLIGATION TO READ AND ACCEPT
ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About,
Feature License, or Feature Update License is provided, please contact
the Eclipse Foundation to determine what terms and conditions govern that
particular Content.
--- snip ---

This looks like a blanket statement
that covers every possibility, that does not require us to customize anything
in the license.html.  Are you saying that we should pare down this
list to precisely the licenses relevant to our features and remove the
"may" and "not limited to" terminology?

I see that many features just copied
this User Agreement verbatim to constitute their feature.htmls.

Thanks,

Christian

---

Christian W. Damus
Component Lead, Eclipse OCL
and EMF-QTV
IBM
Rational Software

Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx

05/30/07 03:02 PM

Please respond to
"eclipse.org-planning-council"        <eclipse.org-planning-council@xxxxxxxxxxx>

To	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
cc	"'Janet Campbell'" <janet.campbell@xxxxxxxxxxx>
Subject	[eclipse.org-planning-council] Re: consuming orbit bundles

Doug, (everyone)
Yes, if a project is consuming Orbit bundles, those bundles must have about.html
files and you need to (1) mention that in your license.html file and (2)
check that the Orbit about.html file is correct. We have discovered that
many/most of the Orbit about.html files have one or more problems. We (Janet
and I) are working on that issue as well, but until then, each consuming
project is responsible for ensuring that the consumed material is correct.
(Yes, I realize that Orbit was supposed to solve that problem, but it hasn't
yet, so you need to check. Sorry.)

- Bjorn

Doug Schaefer wrote: 
I do have a question, though.
We use the LPG runtime plug-in out of orbit which has it’s own about.html
file. Do the features that include that plug-in in the CDT need to mention
that in their license.html file? Or is LPG’s about.html file enough?
 _______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council