Why would I want to make my company leaders wealthier at the expense of my fellow programmers?

Seriously, people, are you all against making an independent living? Or do we all have to work for some IT department?

> As I work for a huge corporation, I must use free software so
> the corporate leaders can buy bigger houses.

Because it is now GPL, you must either pay for the right to use it OR open-source any applications that you create with it. So it is likely that you won’t be able to use Ext-JS any longer for your company projects.

Admin, you said…

> the LGPL license is invalidated by the use of ExtJS in a library

I am not a lawyer, but it is not clear to me that there is a violation (if the license is even valid). GWT-Ext is simply a “wrapper” (not “compiler”), or more specifically, a set of Java API’s that can be used to call the methods of Ext-JS. Note that GWT-Ext itself does not ship with Ext-JS, so it in fact is not actually “using” Ext-JS. All it does is let you write code in Java/GWT that calls the underlying Ext-JS routines.

“If you plan to distribute Ext in a product that will be packaged or sold as a software development library, toolkit or plug-in-based framework (“LIBRARY”), we require that you work with us to establish a specific license that is appropriate.”

As I mention in my blog, I do not package or sell Ext in GWT-Ext. Users are instructed to download and obtain it themselves. http://gwt-ext.com/download/

The basic point as it relates to GWT-Ext is really simple. I mentioned this in my response to Jacks blog but incase it has gotten buried there here it is :

http://jackslocum.com/blog/2008/04/26/ext-js-license-change-and-personal-attacks/

Infact in his original response (which has been edited out on his blog but can be found here http://www.gwt-ext.com/blog/04272008/jacks-response.pdf )

he changes his mind yet again saying :

“That’s fine, you are welcome to stay on Ext 2.0.2. I wonder what happens though when FF3 or IE8 is released?”.

The community cannot be held hostage to his mood on any given day.

So I’d like to wrap up and say there is no license forking that GWT-Ext is creating. We’re going by what the Ext 2.0.2 license permits per what was said and exchanged between us, and mentioned in the past on his forum. Regardless of what he says today or tomorrow, this will not change since he, as he so often admits, is not an attorney.

Sanjiv

What’s it matter as long as we don’t have to pay for anything! Everything must be free! Free, I say, free!

If you ask me for a dime, I will not use your software! As I work for a huge corporation, I must use free software so the corporate leaders can buy bigger houses.

I demand freedom to have everything for free.

Why do we need software developers anyway? There’s already enough software out there! Let’s work to rid the world of software developers!

Instead of the Open-Source Initiative (OSI) mantra, let’s have the Free From Software Developers Initiative (FFSDI) mantra.

Indeed, there are two different situations here as I pointed out: one of your community members, “catplusplus”, announced his fork (OpenEXT) and you simply disagree with Jack Slocum’s replies to this announcement.

You, in fact, are sticking with the last LGPL version of ExtJS and, if I read Jack’s license agreement correctly, it claims that this is not something that can be done because the LGPL license is invalidated by the use of ExtJS in a library.
Unless I am mistaken, you are defending your right to use Ext2.0.2 based on your disagreeing with the original license agreement, thus creating, in effect, something that I am calling, for lack of better words, a “license fork.”

If other entities are able to create a fork and legally back up the move, then the Ext folks can deal with them. Thats a separate issue from GWT-Ext.

I hope this clarifies.

Sanjiv