Written on April 23, 2008 by Stephan Schmidt

GPL and ExtJS for Intranets

2 Comments Comments Icon

My latest thought about ExtJS going GPL. Although ExtJS is GPLv3 and the developers claim (falsely) that your backend needs to be GPL too when generating code that contains ExtJS, for internal/intranet applications you still can use ExtJS as you’re not distributing ExtJS.

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.

Comments

Vick

May 7th, 2008

How about extranets? As in a publicly available web site?

How about password-protected web sites (such as an online banking application for instance)?

What is your understanding about the GPL in these cases if we use extJs? Thx!

stephan

May 7th, 2008

IANAL and I’m out of my waters. But a standard GPL should not be a problem for extranets. But that is just the common understanding of the GPL as I see it, Ext LLC seems to see this different.

The AGPL would be another thing:

http://en.wikipedia.org/wiki/Affero_General_Public_License

“The GNU AGPL is similar to the GNU General Public License, except that it has an additional section to cover use over a computer network. ”

This was probably what they ment but for some reason didn’t use.