Ext JS responds with Open Source FLOSS Exceptions

Why Should PHP ever be taught in school?

Happy New Year Folks! Let's keep on blogging. This posting by Ka-Ping Yee on why PHP should never be taught is precisely why PHP should be taught. If something is popular but hard to understand then we need an education process. To just shake our hea...

Jack Slocum and his team are listening, and appear to be working with the community to clear things up:

With our recent change to the GPL v3 some concerns have been brought up by the Ext Community. We are hoping to address some of those concerns via community discussion of two new FLOSS exceptions.

The first step for us is the Open Source License Exception for Extensions. It is currently in draft status and we are seeking input from the community before we have it finalized.

The intention of this exception is to allow for more liberal licensing of extensions, language packs, themes and open source developer toolkits and frameworks for Ext libraries under a variety of open source licenses. (Note: this exception is not for applications and does not grant any exception for the library itself. A FLOSS exception on the libraries for open source applications will be addressed in the exception discussed in ?Next Up? below).

He is looking for input and feedback. You can see the latest draft, and if you have thoughts join the discussion.

This exception is the first step, with more to come:

After the Extension Exception is complete, the next step will be drafting a FLOSS exception similar to the one by MySQL AB for both Ext JS and Ext GWT.

This exception will for open source applications that use Ext JS. It will have a few distinct additional grants the Extension Exception doesn?t have (e.g. ?bundling? will be ok) but won?t be applicable to extensions or toolkits, as that?s what the Extension Exception is for.

Quick work, and the fact that he is joining and leading the discussion is huge.