Commercial License Question

[Bobafart]

Hello

I am thinking about a commercial license for the Developer License.

If I buy a license, is that license good forever? That is, say 2 years down the road, when version 10 is released with a whole plethora of new features, etc, will my license that I purchase today still be effective without having to spend more money for a Developer License upgrade?

[Bobafart]

Also, what kind of support license do you get with the Developer License? (I don't see any specific information about this in the "Store" section of the new website).

[jack.slocum]

The license is a classic commercial software license. It is good for that version forever. We also include 1 year of free minor upgrades.

The licenses and support subscriptions are "a la carte". A commercial license does not include support and a support contract does not include a commercial license. This way people can buy exactly what they want. At the top of the commercial license and support subscriptions pages, there is a gray highlighted block with similar text.

Thanks!

[KimH]

The license is a classic commercial software license. It is good for that version forever. We also include 1 year of free minor and major upgrades.

What I understand is that if you but a license as pr. 15. april when 1.0 is released, then you can use whatever version made public between 15th April 2007 and 15th April 2008. If a 4.2 version is released on 14th April 2008 and a version 4.9 on 16th April 2008 then you will be able to use 4.2 version for the next 100000 years but not the 4.9.

[nbinder]

What I don't understand is the following:

I am planning to use ext on my website. The site is somehow commercial (we don't earn money, but we do have advertisements to pay the servers and stuff), but for me the open source licence would be enough as I don't modify the javascripts and leave then readable for everybody on the server.

So: Is it right that way? Of course a website also has a bunch of scripts (php) that are not open source and will never be... but that has nothing to do with ext, or am I wrong?

Your licence page is a bit confusing... :-?

[JeffHowden]

The big question is whether or not you think you need a commercial license to satisfy any quirky legal eagles at the company you work for. If little to none of that statement applies to you, then probably a straight up LGPL (which has zero to do with the price for a commercial license) is sufficient for you.

Clear as mud?

[nbinder]

As the company is basically me myself (for the technical part of it), thats not such a big problem.

It's more a basic question if you have to say that you are selling a product if the product is a web site which does include advertisements and a member fee. But at the same time the site never sells ext itself, because access to the ext lib is always possible, not only on the free part of the site....

As far as I see it here, most of you are talking about applications and therefore sold products, but a website is somehow different, as everybody has access and as javascript is not compiled it's open source at any time.

[justheatingup]

nbinder

Here's my take. EXT 1.0 is dual licensed LGPL and Commercial. Although, that might mean a lot of things to a lot of people (i have my own take on it), the best way to clear up any confusion is to purchase a license.

Mainly this clears up any confusion as to the LGPL and your "commercial site". Just make sure you feel comfortable with the commercial license terms and conditions. Lastly, and I believe more importantly, you are supporting Jack.

But the choice is up to you. If I said consult an attorney, you'd be out a few grand just by mentioning LGPL. So my advice is support the man that made this happen, and sleep better for it.

[nbinder]

justheatingup

That's a good point... as I like the project and wanted to support it anyway buying a licence will be the best solution.

[sycophant]

For our usage of Ext at this stage (still limited to the older Yui-Ext incarnation, but will be moving to ExtJS) we are happy with the LGPL licence. For our company the application in which we are making most use of Ext is essentially a spec application. We are writing it on our own time, self-funding it, but later plan to sell it to clients as a solution.

At the point where our product becomes a serious commercial product for us, then we will invest in a commercial licence - more to support the project than out of a concern for the licencing terms.

I am very thankful for projects like ExtJS with a dual OSS/Commercial model, which allow us to utilise the tools in a legal way for no cost while we are especially budget concern, but offer commercial-level support also for later down the track when our budgets allow that.