-
The plain LGPL has no field-of-use restriction. The restriction added in the Ext license present a few major problems: 1. The new license is no longer compatible with the plain GPL. The plain GPL (any version) does not permit additional restrictions on field of use. 2. The new license would not be considered to be a free software license by FSF, nor an open source license by OSI. I can tell you this with absolute certainty, since one of my duties when I worked for FSF was evaluating licenses. 3. The new license is confusing. It says it's LGPL, but then gives up on many of the most important characteristics of the LGPL. 4. I have no idea what a "developer toolkit" is. Unfortunately, under these circumstances, I cannot recommend the use of current versions of Ext. I will be recommending that we peg ourselves to the latest version of Ext which was available under the plain LGPL. This is what On Fri, 2008-03-28 at 18:40 -0400, Ext Licensing wrote: > Hi David, > > Thank you for you interest in ExtJS. Ext is licensed under the Ext > License http://extjs.com/license. To help our community understand > our intentions, we refer to the LGPL and grant usage under the terms > of the LGPL so long as the product is not a developer toolkit. I hope > this clears up any ambiguity. I noticed that TOPP is an avid > supporter of open source. I hope that you find our restrictions > reasonable enough to use ExtJS with your projects. Please let me know > if I can answer any more of your questions. > > Warm regards, > Abraham Elias > > On Fri, Mar 28, 2008 at 5:33 PM, David Turner <novalis@...> > wrote: > Is ext truly available under the LGPLv3, with no additional > restrictions? Your licensing page[1] makes this very unclear. > > > > > > [1] http://extjs.com/license > > > !DSPAM:4019,47ed7402106838362916074!
- Thread Outline:
-
-
Re: Is ext truly available under the LGP ...
by
novalis
-
Re: Re: Is ext truly available under th ...
by
magicbronson
- Re: Re: Is ext truly available under th ... by "Sebastian Benthall" <sbenthall@...>
- Re: Re: Is ext truly available under th ... by douglas
- Re: Is ext truly available under the LGP ... by "Ext Licensing" <licensing@...>
-
Re: Re: Is ext truly available under th ...
by
magicbronson
-
Re: Re: Is ext truly available under th ...
by
ianb
-
Re: Re: Is ext truly available under th ...
by
novalis
- Re: Re: Is ext truly available under th ... by Jacqueline Arasi <jarasi@...>
-
Re: Re: Is ext truly available under th ...
by
novalis
-
Re: Is ext truly available under the LGP ...
by
novalis
-
On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > The plain LGPL has no field-of-use restriction. The restriction added > in the Ext license present a few major problems: > > 1. The new license is no longer compatible with the plain GPL. The > plain GPL (any version) does not permit additional restrictions on field > of use. > > 2. The new license would not be considered to be a free software license > by FSF, nor an open source license by OSI. I can tell you this with > absolute certainty, since one of my duties when I worked for FSF was > evaluating licenses. > > 3. The new license is confusing. It says it's LGPL, but then gives up > on many of the most important characteristics of the LGPL. > > 4. I have no idea what a "developer toolkit" is. > > Unfortunately, under these circumstances, I cannot recommend the use of > current versions of Ext. I will be recommending that we peg ourselves > to the latest version of Ext which was available under the plain LGPL. > This is what [sorry, accidentally hit send early]. This is what we appear to be using now.
-
It really rocks to have a local expert on software licenses. Can I get a what what? On Mon, Mar 31, 2008 at 3:07 PM, David Turner <novalis@...> wrote: > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > > The plain LGPL has no field-of-use restriction. The restriction added > > in the Ext license present a few major problems: > > > > 1. The new license is no longer compatible with the plain GPL. The > > plain GPL (any version) does not permit additional restrictions on field > > of use. > > > > 2. The new license would not be considered to be a free software license > > by FSF, nor an open source license by OSI. I can tell you this with > > absolute certainty, since one of my duties when I worked for FSF was > > evaluating licenses. > > > > 3. The new license is confusing. It says it's LGPL, but then gives up > > on many of the most important characteristics of the LGPL. > > > > 4. I have no idea what a "developer toolkit" is. > > > > Unfortunately, under these circumstances, I cannot recommend the use of > > current versions of Ext. I will be recommending that we peg ourselves > > to the latest version of Ext which was available under the plain LGPL. > > This is what > > [sorry, accidentally hit send early]. > > This is what we appear to be using now. > > > > -- > Archive: > http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 > To unsubscribe send an email with subject unsubscribe to > opencore-dev@.... Please contact > opencore-dev-manager@... for questions. > >
-
what what On Mon, Mar 31, 2008 at 3:13 PM, Joshua Bronson <jabronson@...> wrote: > It really rocks to have a local expert on software licenses. Can I get a > what what? > > > > On Mon, Mar 31, 2008 at 3:07 PM, David Turner <novalis@...> wrote: > > > > > > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > > > The plain LGPL has no field-of-use restriction. The restriction added > > > in the Ext license present a few major problems: > > > > > > 1. The new license is no longer compatible with the plain GPL. The > > > plain GPL (any version) does not permit additional restrictions on field > > > of use. > > > > > > 2. The new license would not be considered to be a free software license > > > by FSF, nor an open source license by OSI. I can tell you this with > > > absolute certainty, since one of my duties when I worked for FSF was > > > evaluating licenses. > > > > > > 3. The new license is confusing. It says it's LGPL, but then gives up > > > on many of the most important characteristics of the LGPL. > > > > > > 4. I have no idea what a "developer toolkit" is. > > > > > > Unfortunately, under these circumstances, I cannot recommend the use of > > > current versions of Ext. I will be recommending that we peg ourselves > > > to the latest version of Ext which was available under the plain LGPL. > > > This is what > > > > [sorry, accidentally hit send early]. > > > > This is what we appear to be using now. > > > > > > > > -- > > Archive: > http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 > > > > > > > > To unsubscribe send an email with subject unsubscribe to > opencore-dev@.... Please contact > opencore-dev-manager@... for questions. > > > > > >
-
-
Do you mean that 1.x is under the bastardized LGPL ? I had thought it was just plain LGPL... What a disappointment... On Mar 31, 2008, at 3:07 PM, David Turner wrote: > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: >> The plain LGPL has no field-of-use restriction. The restriction >> added >> in the Ext license present a few major problems: >> >> 1. The new license is no longer compatible with the plain GPL. The >> plain GPL (any version) does not permit additional restrictions on >> field >> of use. >> >> 2. The new license would not be considered to be a free software >> license >> by FSF, nor an open source license by OSI. I can tell you this with >> absolute certainty, since one of my duties when I worked for FSF was >> evaluating licenses. >> >> 3. The new license is confusing. It says it's LGPL, but then gives >> up >> on many of the most important characteristics of the LGPL. >> >> 4. I have no idea what a "developer toolkit" is. >> >> Unfortunately, under these circumstances, I cannot recommend the >> use of >> current versions of Ext. I will be recommending that we peg >> ourselves >> to the latest version of Ext which was available under the plain >> LGPL. >> This is what > > [sorry, accidentally hit send early]. > > This is what we appear to be using now. > > > > -- > Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 > To unsubscribe send an email with subject unsubscribe to opencore-dev@... > . Please contact opencore-dev-manager@... for > questions. > > > !DSPAM:4037,47f13710317593362379201! >
-
I don't know when the changeover happened, since they appear to not have an open svn repository (yuck). Some of the files we have say "see http://extjs.com/licensing for license". Some say "LGPL 2.1", with no mention of additional restrictions. Googling reveals various versions under the LGPL, but since everyone seems to use the mangled (compressed) version, rather than the source, it's hard to tell anything. Do we know where we can find the source to what we have? On Mon, 2008-03-31 at 15:15 -0400, Douglas Mayle wrote: > Do you mean that 1.x is under the bastardized LGPL ? I had thought it > was just plain LGPL... What a disappointment... > > On Mar 31, 2008, at 3:07 PM, David Turner wrote: > > > > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > >> The plain LGPL has no field-of-use restriction. The restriction > >> added > >> in the Ext license present a few major problems: > >> > >> 1. The new license is no longer compatible with the plain GPL. The > >> plain GPL (any version) does not permit additional restrictions on > >> field > >> of use. > >> > >> 2. The new license would not be considered to be a free software > >> license > >> by FSF, nor an open source license by OSI. I can tell you this with > >> absolute certainty, since one of my duties when I worked for FSF was > >> evaluating licenses. > >> > >> 3. The new license is confusing. It says it's LGPL, but then gives > >> up > >> on many of the most important characteristics of the LGPL. > >> > >> 4. I have no idea what a "developer toolkit" is. > >> > >> Unfortunately, under these circumstances, I cannot recommend the > >> use of > >> current versions of Ext. I will be recommending that we peg > >> ourselves > >> to the latest version of Ext which was available under the plain > >> LGPL. > >> This is what > > > > [sorry, accidentally hit send early]. > > > > This is what we appear to be using now. > > > > > > > > -- > > Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 > > To unsubscribe send an email with subject unsubscribe to opencore-dev@... > > . Please contact opencore-dev-manager@... for > > questions. > > > > > > > > > > > > -- > Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990935438 > To unsubscribe send an email with subject unsubscribe to opencore-dev@.... Please contact opencore-dev-manager@... for questions. > > > !DSPAM:4019,47f1391d326302092453641! >
-
Here is ext 1.1 uncompressed (attached). I can give you the whole bundle if you need it; this is just the core file. Nick On Mar 31, 2008, at 3:30 PM, David Turner wrote: > I don't know when the changeover happened, since they appear to not > have > an open svn repository (yuck). Some of the files we have say "see > http://extjs.com/licensing for license". Some say "LGPL 2.1", with no > mention of additional restrictions. Googling reveals various versions > under the LGPL, but since everyone seems to use the mangled > (compressed) > version, rather than the source, it's hard to tell anything. Do we > know > where we can find the source to what we have? > > On Mon, 2008-03-31 at 15:15 -0400, Douglas Mayle wrote: >> Do you mean that 1.x is under the bastardized LGPL ? I had thought >> it >> was just plain LGPL... What a disappointment... >> >> On Mar 31, 2008, at 3:07 PM, David Turner wrote: >> >>> >>> On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: >>>> The plain LGPL has no field-of-use restriction. The restriction >>>> added >>>> in the Ext license present a few major problems: >>>> >>>> 1. The new license is no longer compatible with the plain GPL. The >>>> plain GPL (any version) does not permit additional restrictions on >>>> field >>>> of use. >>>> >>>> 2. The new license would not be considered to be a free software >>>> license >>>> by FSF, nor an open source license by OSI. I can tell you this >>>> with >>>> absolute certainty, since one of my duties when I worked for FSF >>>> was >>>> evaluating licenses. >>>> >>>> 3. The new license is confusing. It says it's LGPL, but then gives >>>> up >>>> on many of the most important characteristics of the LGPL. >>>> >>>> 4. I have no idea what a "developer toolkit" is. >>>> >>>> Unfortunately, under these circumstances, I cannot recommend the >>>> use of >>>> current versions of Ext. I will be recommending that we peg >>>> ourselves >>>> to the latest version of Ext which was available under the plain >>>> LGPL. >>>> This is what >>> >>> [sorry, accidentally hit send early]. >>> >>> This is what we appear to be using now. >>> >>> >>> >>> -- >>> Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 >>> To unsubscribe send an email with subject unsubscribe to opencore-dev@... >>> . Please contact opencore-dev-manager@... for >>> questions. >>> >>> >>> >>> >> >> >> >> -- >> Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990935438 >> To unsubscribe send an email with subject unsubscribe to opencore-dev@... >> . Please contact opencore-dev-manager@... for >> questions. >> >> >> >> > > > > -- > Archive: http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206991811100 > To unsubscribe send an email with subject unsubscribe to opencore-dev@... > . Please contact opencore-dev-manager@... for > questions. > > > !DSPAM:4028,47f13c5f13302143011171! > -- Nick Grossman The Open Planning Project -- topp.openplans.org nickyg@... (917) 825-6590
-
So this is 1.1. We need to switch down to 1.0. On Mon, 2008-03-31 at 15:37 -0400, Nick Grossman wrote: > Here is ext 1.1 uncompressed (attached). I can give you the whole > bundle if you need it; this is just the core file. > > > > !DSPAM:4019,47f13e2316701849620573! > > > Nick > > On Mar 31, 2008, at 3:30 PM, David Turner wrote: > > I don't know when the changeover happened, since they appear to not > > have > > an open svn repository (yuck). Some of the files we have say "see > > http://extjs.com/licensing for license". Some say "LGPL 2.1", with > > no > > mention of additional restrictions. Googling reveals various > > versions > > under the LGPL, but since everyone seems to use the mangled > > (compressed) > > version, rather than the source, it's hard to tell anything. Do we > > know > > where we can find the source to what we have? > > > > On Mon, 2008-03-31 at 15:15 -0400, Douglas Mayle wrote: > > > Do you mean that 1.x is under the bastardized LGPL ? I had > > > thought it > > > was just plain LGPL... What a disappointment... > > > > > > On Mar 31, 2008, at 3:07 PM, David Turner wrote: > > > > > > > > > > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > > > > > The plain LGPL has no field-of-use restriction. The > > > > > restriction > > > > > added > > > > > in the Ext license present a few major problems: > > > > > > > > > > 1. The new license is no longer compatible with the plain > > > > > GPL. The > > > > > plain GPL (any version) does not permit additional > > > > > restrictions on > > > > > field > > > > > of use. > > > > > > > > > > 2. The new license would not be considered to be a free > > > > > software > > > > > license > > > > > by FSF, nor an open source license by OSI. I can tell you > > > > > this with > > > > > absolute certainty, since one of my duties when I worked for > > > > > FSF was > > > > > evaluating licenses. > > > > > > > > > > 3. The new license is confusing. It says it's LGPL, but then > > > > > gives > > > > > up > > > > > on many of the most important characteristics of the LGPL. > > > > > > > > > > 4. I have no idea what a "developer toolkit" is. > > > > > > > > > > Unfortunately, under these circumstances, I cannot recommend > > > > > the > > > > > use of > > > > > current versions of Ext. I will be recommending that we peg > > > > > ourselves > > > > > to the latest version of Ext which was available under the > > > > > plain > > > > > LGPL. > > > > > This is what > > > > > > > > [sorry, accidentally hit send early]. > > > > > > > > This is what we appear to be using now. > > > > > > > > > > > > > > > > -- > > > > Archive: > > > > http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990440574 > > > > To unsubscribe send an email with subject unsubscribe to > > > > opencore-dev@... > > > > . Please contact opencore-dev-manager@... for > > > > questions. > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Archive: > > > http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206990935438 > > > To unsubscribe send an email with subject unsubscribe to > > > opencore-dev@.... Please contact > > > opencore-dev-manager@... for questions. > > > > > > > > > > > > > > > > > > > > -- > > Archive: > > http://www.openplans.org/projects/opencore/lists/opencore-dev/archive/2008/03/1206991811100 > > To unsubscribe send an email with subject unsubscribe to > > opencore-dev@.... Please contact > > opencore-dev-manager@... for questions. > > > > > > > > > > -- > Nick Grossman > The Open Planning Project -- topp.openplans.org > nickyg@... > (917) 825-6590 > > > > > !DSPAM:4019,47f13e2316701849620573!
-
-
-
-
Hi David, Ext has been under the Ext license since release 1.1. So as long as you are using 1.0.x, you are fine. Regards, Jack Slocum On Mon, Mar 31, 2008 at 3:07 PM, David Turner <novalis@...> wrote: > > On Mon, 2008-03-31 at 15:07 -0400, David Turner wrote: > > The plain LGPL has no field-of-use restriction. The restriction added > > in the Ext license present a few major problems: > > > > 1. The new license is no longer compatible with the plain GPL. The > > plain GPL (any version) does not permit additional restrictions on field > > of use. > > > > 2. The new license would not be considered to be a free software license > > by FSF, nor an open source license by OSI. I can tell you this with > > absolute certainty, since one of my duties when I worked for FSF was > > evaluating licenses. > > > > 3. The new license is confusing. It says it's LGPL, but then gives up > > on many of the most important characteristics of the LGPL. > > > > 4. I have no idea what a "developer toolkit" is. > > > > Unfortunately, under these circumstances, I cannot recommend the use of > > current versions of Ext. I will be recommending that we peg ourselves > > to the latest version of Ext which was available under the plain LGPL. > > This is what > > [sorry, accidentally hit send early]. > > This is what we appear to be using now. > >
-
-
OK, so to recap on this licensing thing: 1. Is there any chance we can convince Ext to release their library under an open source license? E.g., GPL-with-exemptions, instead of fake-LGPL-with-restrictions? 2. Do we want to make a stink about this? Either to help 1 happen, or just out of principle? Or can we just rely on the FSF to make a stink about it? 3. If there is a chance of 1, what is the timeline when we'll know? Like, how long before we give up hope? 4. Is reverting to 1.0 easy (if, as I understand, we're on 1.1 and only 1.0 has acceptable licensing)? 5. If we choose to ditch Ext, when can we do that? Presumably not now. If reverting to 1.0 is hard, and we plan to move off Ext entirely (since staying pegged to an old version indefinitely isn't a good idea), should we just stay with what we have and plan to fix this later? 6. And if we ditch Ext, what do we use instead? (Relevant now since block party needs to use something) Ian
-
On Wed, 2008-04-02 at 12:01 -0500, Ian Bicking wrote: > OK, so to recap on this licensing thing: [I'm just answering the licensing side, since that's what I'm familiar with] > 1. Is there any chance we can convince Ext to release their library > under an open source license? E.g., GPL-with-exemptions, instead of > fake-LGPL-with-restrictions? It's worth a try. I'm happy to write that email. > 2. Do we want to make a stink about this? Either to help 1 happen, or > just out of principle? Or can we just rely on the FSF to make a stink > about it? FSF doesn't really have the resources to go after everyone who is misusing the licenses. > 3. If there is a chance of 1, what is the timeline when we'll know? > Like, how long before we give up hope? I have been getting replies fairly quickly, and they have been polite and clear.
-
Hey All, Cholmes and I are looking into this in order to make a decision about what is best for TOPP. We may come back with some questions for you as we move towards an organizational decision. We are hoping to move fairly quickly on this, and we'll report back. Please hang tight while we move forward. -JA On Apr 2, 2008, at 2:02 PM, David Turner wrote: > > On Wed, 2008-04-02 at 12:01 -0500, Ian Bicking wrote: >> OK, so to recap on this licensing thing: > > [I'm just answering the licensing side, since that's what I'm familiar > with] > >> 1. Is there any chance we can convince Ext to release their library >> under an open source license? E.g., GPL-with-exemptions, instead of >> fake-LGPL-with-restrictions? > > It's worth a try. I'm happy to write that email. > >> 2. Do we want to make a stink about this? Either to help 1 >> happen, or >> just out of principle? Or can we just rely on the FSF to make a >> stink >> about it? > > FSF doesn't really have the resources to go after everyone who is > misusing the licenses. > >> 3. If there is a chance of 1, what is the timeline when we'll know? >> Like, how long before we give up hope? > > I have been getting replies fairly quickly, and they have been polite > and clear. > > > > -- > Archive: http://www.openplans.org/projects/opencore/lists/opencore- > dev/archive/2008/04/1207159354964 > To unsubscribe send an email with subject unsubscribe to opencore- > dev@.... Please contact opencore-dev- > manager@... for questions. > > > !DSPAM:4004,47f3ca75190247180515871! >
-
Hey Jackie, Could we get a status update on this? Chris On Apr 2, 2008, at 2:23 PM, Jacqueline Arasi wrote: > Hey All, > Cholmes and I are looking into this in order to make a decision > about what is best for TOPP. We may come back with some questions > for you as we move towards an organizational decision. We are > hoping to move fairly quickly on this, and we'll report back. > Please hang tight while we move forward. > > -JA > On Apr 2, 2008, at 2:02 PM, David Turner wrote: > >> >> On Wed, 2008-04-02 at 12:01 -0500, Ian Bicking wrote: >>> OK, so to recap on this licensing thing: >> >> [I'm just answering the licensing side, since that's what I'm >> familiar >> with] >> >>> 1. Is there any chance we can convince Ext to release their library >>> under an open source license? E.g., GPL-with-exemptions, instead of >>> fake-LGPL-with-restrictions? >> >> It's worth a try. I'm happy to write that email. >> >>> 2. Do we want to make a stink about this? Either to help 1 >>> happen, or >>> just out of principle? Or can we just rely on the FSF to make a >>> stink >>> about it? >> >> FSF doesn't really have the resources to go after everyone who is >> misusing the licenses. >> >>> 3. If there is a chance of 1, what is the timeline when we'll know? >>> Like, how long before we give up hope? >> >> I have been getting replies fairly quickly, and they have been polite >> and clear. >> >> >> >> -- >> Archive: http://www.openplans.org/projects/opencore/lists/opencore- >> dev/archive/2008/04/1207159354964 >> To unsubscribe send an email with subject unsubscribe to opencore- >> dev@.... Please contact opencore-dev- >> manager@... for questions. >> >> >> > > > > -- > Archive: http://www.openplans.org/projects/opencore/lists/opencore- > dev/archive/2008/04/1207160639624 > To unsubscribe send an email with subject unsubscribe to opencore- > dev@.... Please contact opencore-dev- > manager@... for questions. > > > !DSPAM:4017,47f3cf57208361012714783! >
-
-
-
text.html (text/html) 2.3 kB