[Psc] [Fwd: [Fwd: Re: IP and Licensing Questions]]
Tim Schaub
tschaub at opengeo.org
Fri May 15 02:15:26 CEST 2009
For those that didn't get the message I mistakenly sent to the OL PSC...
-------- Original Message --------
Subject: [Fwd: Re: IP and Licensing Questions]
Date: Thu, 14 May 2009 17:34:03 -0600
From: Tim Schaub
To: psc at openlayers.org
CC: Chris Holmes
I'll send an update when I hear back (and send them a friendly reminder
if I don't).
Tim
-------- Original Message --------
Subject: Re: IP and Licensing Questions
Date: Tue, 12 May 2009 18:39:32 -0400
From: Ext Licensing <licensing at extjs.com>
To: Tim Schaub
References: <4A09F9C3.5090708 at opengeo.org>
Tim:
Thanks for your einquiry and efforts. I am passing your note to Abe,
our CEO, to better understand where you are headed and assist in
answering your questions.
~ The Ext Team
On Tue, May 12, 2009 at 6:35 PM, Tim Schaub wrote:
Hello-
I am writing on behalf of a community of developers working on a
project that extends ExtJS (2.x) classes with mapping functionality
from the OpenLayers library. We have a number of questions related
to licensing (and intellectual property) that we are hoping to get
answers on.
First, we have been calling our project GeoExt, and wanted to make
sure the name was appropriate for us to use. Below is a mockup of
our issue tracker with a logo at the head.
http://img.skitch.com/20090409-jksimuqt2axkrciw386bx2n3f4.png.
Please let us know if the name and look of the logo are acceptable
for us to use.
Our library [1] extends Ext components and data utilities with
mapping functionality from OpenLayers [2]. Our plan has been to
distribute GeoExt under a BSD license and to include OpenLayers
(with a BSDish license) in our releases. We will provide
instructions with our releases on obtaining Ext from extjs.com
<http://extjs.com/>. Our understanding is that we meet the terms of
the Open Source License Exception for Development [3].
We have received some questions from interested application
developers regarding licensing of applications built with GeoExt and
Ext. I'll enumerate them below. Thanks for any answers you are
able to provide.
1) If an application includes a script that is a minified version
of the
Ext source and is not produced by the Ext build tools [4] (e.g.
minified
with YUICompressor), I assume this is considered "Conveying Non-Source
Forms" and not "Conveying Modified Source Versions" under GPL v3. Is
this assumption correct?
If so, the GPL says the object code provider must also convey the
machine-readable source. One of the ways this can be done is to offer
access to the source from a designated place (point 6.d). Is it enough
for the application provider to include a notice in the minified code
that references the license and gives instruction to download the
source
from Ext? I'm assuming the application provider doesn't have to
provide
access to anything else themselves (e.g. the tools used to minify the
source or the source itself).
2) A typical application would include Ext and application code that
calls Ext methods. The Open Source License Exception for
Applications [5] suggests that code that is independent of the
library may be distributed under one of the listed licenses (point
2.a and the paragraph preceding it). Is application code that
relies on Ext (calls methods and accesses properties) considered
independent and can this code be distributed under one of the listed
licenses (assuming other terms are met)?
Thanks for your responses. We're excited to be using Ext and to be
introducing developers of mapping applications to a rich new set of
features.
Tim
[1] http://svn.geoext.org/core/trunk/geoext/lib/
[2] http://openlayers.org/
[3] http://extjs.com/products/ux-exception.php
[4] http://extjs.com/products/extjs/build/
[5] http://extjs.com/products/floss-exception.php
--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
--
Tim Schaub
OpenGeo - http://opengeo.org
Expert service straight from the developers.
More information about the Psc
mailing list