Let's say I create a CMS that uses ExtJS.
I want to avoid the license fee, so I open-source the CMS on github.
Now let's imagine that I make your friend Dave a website that uses my CMS. I spend three hundred hours designing a logo and layout. Can I charge a fee for this, and would I be obliged to open-source Dave's website too or is it enough to just open-source the CMS?
I find this LPGL license a little confusing. Say hi to Dave for me.
Only ExtJS code prior to 2.1 is under LGPL. It currently uses GPLv3. That means if you distribute it, "the entire work, as a whole" must be licensed under GPLv3. The entire work may include code directly connected to ExJS. But "separate and independent works, which are not by their nature extensions of the covered work" (which probably includes server code) don't have to be GPLv3. So the way I interpret it, only code (e.g. client JS you develop) that tightly extends Ext would have to be released. See also this FAQ.
Regardless, you can charge as much as you want for services and/or the CMS itself.
IANAL.
ExtJS GPL Licence means that if you are using ExtJS under GPL Licence, and not modifying ExtJS itself, then you are Free to use ExtJS in whatever manner on any Website. But if you take ExtJS and start modifying ExtJS itself ( to make some better 'Super-Duper-ExtJS' Library ), then you have to share that with everyone, because if you start selling 'Super-Duper-ExtJS' to your Clients, then whats going to happen is that 'ExtJS-Company' finds itself Competing with Itself. I dont think you need to share your 'Website's Source-code' in any case. If you need to share your 'Websites source-code' ifself with other People while using ExtJS-GPL, then only the ExtJS-GPL Licence would start looking absurd, and you need to start looking at jQueryUI or DOJO ! But I dont think that 'ExtJS-Company' means to share your Websites-source just for the reason that you used their ExtJS Library ! What say .......
