the blog for developers

Another ExtJS GPL thought – Should extensions switch to the GPL?

Sorry, this would better go to twitter – but I’m not twittering.

Another thought. And not because I want to bash ExtJS, but because I’ve been interested into the GPL, open source licensing and the implications for over a decade.

IANAL. The best situation for the company behind ExtJS would be if extension developers stay with the LGPL for their extension (or switch to a more liberal Apache license). The people who buy the OEM license from Ext can then use the extension. If someone releases his ExtJS extension as GPL, to be more “in line” with ExtJS, people with the OEM license cannot use the plugin, because it’s GPL (they can use the extension in a way that their customer need to download and install the extension on his own, but this is most often too cumbersome for customers. They are not allowed to distribute their commercial application with the extension or any code which references the extension).

The plugin writers do not gain anything for staying with the LGPL license, but Ext LLC gains a lot. It makes their OEM license much more valuable. If every Plugin writer switches to the GPL version, this could have an impact on the OEM sale. Especially because most enterprise won’t touch GPL software.

The best for a plugin author is to also go to a dual GPL/commercial license.

Very interesting situation.

Update: Very interesting

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt is head of development at brands4friends. He has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.
Leave a reply.

Comments

sean

A few years ago superwaba did the same thing. Look how they played out – they died.

stephan

Most likely ExtJS will be history too. If not, then I would really be interested in why not. This would be interesting for open source business models. The current canon says this won’t work.

Martin

I’m developing web application “as a service”. I never distribute it anywhere. I’ve relicensed all my work to GPL3 without problem. You are not forced to give sources away if there is no distribution. And there is not.

[...] No signal, no noise. « Another ExtJS GPL thought – Should extensions switch to the GPL? [...]

Fear not. I think we’re all going to find this has been loudly blown out of proportion.

“Open Source License Exception for Extensions
Draft .26, April 28th, 2008″
http://extjs.com/products/ux-exception.php

stephan

@Chris: Perhaps I’m stupid – most of the time watching the world I think this is the only explanation that makes sense – but the exception does not change anything. As written in the post, liberal extensions do only help Ext LLC, no-one else. This is just smoke and mirror.

As predicted in the post “The best situation for the company behind ExtJS would be if extension developers stay with the LGPL for their extension (or switch to a more liberal Apache license).”

stephan

What would help is “[...] applications [...] for that we are working on another FLOSS Exception.” We’ll see.

But in the end this will not change the point the companies will not touch GPL stuff.

@Stephen: What do you think of the gwt-ext folks selling gwt-plus licenses?

try doing a search for “purchase gwt plus license”. you’ll find this obscure page which doesn’t seem to be heavily advertised on any of their main sites.

Are they under-cutting ExtJS?

@Stephan: (sorry for typo in your name in last comment)

stephan

@Chris: Not sure, GWT Plus is something additional to GWT Ext, not just something relicensed.

There is a lot going on with Ext and licensing, perhaps best to wait a month and see how the dust settles. Perhaps the internet and forum discussions started to change things – perhaps not and it’s just smoke and mirrors.

stephan

@Chris: NP, I’m used to that

concerned ux dev

http://extjs.com/products/ux-exception.php

notice how the list doesn’t specifically contain the GPL – they push more to the lgpl, funny how they want ux devs to write lgpl but it is not good enough for themselves
They want ux to be compatible with oem and commercail licensed ux.

extjs extension developers should release under GPL v3 just like they do – if the license is so good why are they making exceptions for it. There is only one word that i can see Greed. Ext was built off the back of liberally licensed software.

[...] version 1.0 of its SDK for developing GWT applications with the Ext JS library. Despite some controversy around Ext’s licensing strategy (namely the switch from LGPL to GPL), Ext GWT is currently one of [...]

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

NoSQL Guy

NoSQL: The Dawn of Polyglot Persistence

The dark side of NoSQL

Essential storage tradeoff: Simple Reads vs. Simple Writes

Sharding destroys the goals of your relational database

The unholy legacy of databases

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?