Where this gets complicated is that Jack decided to license the assets under a different license, allowing him to retain all rights. I would like to make very clear that it’s his work and he can do whatever he wants with it. I am just narrating, here. He also added a clause that supposedly completely voids the LGPL license if someone attempted to use his work to create a derivative framework.
After a lot of moaning in the community - to the drum of “that’s a GNU license, man, the whole idea is that you cannot add restrictions!“, he decided to change the LGPL license to a pure GPL one, while retaining a pure commercial license on the side. I’ll bet he thought, at that point, “At least now things are clear.”
Well, that was only the beginning of a real sh*tstorm that threatens to cause a lot of damage to everyone involved, culminating -fleetingly, to be sure- with Sanjiv Jivan’s scathing blog post. Sanjiv, if I am correct, wrote a Ext “compiler” for the GWT library, called GWT-Ext - note that there is another project, apparently endorsed by Jack, that connects ExtJS and GWT. Sanjiv decided that he would fork the last LGPL release of ExtJS and start a new project. You may remember that Jack tried to prevent this by adding a provision in his license agreement.
The crux of Sanjiv’s beef with Jack Slocum is this: Jack created a great product, led people to believe that it was truly open-source when it wasn’t, and doesn’t understand open-source licenses. Jack is greedy. Now, the crux of Jack’s beef with Sanjiv is this: Sanjiv created a nice tool based on hits product, doesn’t understand open-source licenses and, oh, is greedy.
So, our protagonists are not talking to each other. This love story was
consumed a long time ago. And potential “corporate” customers, like me, are
revisiting the possibility of building their product on top of pure JQuery
extensions and living happily ever after.
Now, in a move that would shame any seasoned soap opera writer, a new character enters left stage. And her name is OpenEXT. Contrary to what Dion Almar wrote, it is not a fork: the idea is to create patches that can be dropped on top of ExtJS. Now, I am curious: was Dion right when he posted his own piece on the topic? After all, things seem to change at a meteoric pace around here.
Anyway, stay tuned for even more implausible developments!