Re: Does new Community version change C API licensing?

[Kaj Arnö]

Warren,

As part of today's Press Release on MySQL Enterprise, there's no change 
in the client side licensing. However, as part of the MySQL Winter of 
Code and the Connector contest, we have something in store which we will 
be sharing with you next week.

As for free-of-charge, the need to buy OEM licenses is only related to 
*distributing* applications, not using MySQL in-house. This is how it 
was before, and this is how it is today. We do not *require* in-house 
users of MySQL to subscribe to MySQL Enterprise.

However, we definitely want to make MySQL Enterprise *attractive* for 
business users who have MySQL in production use, by providing them added 
value on top of what MySQL Community has.

So: For client licensing, nothing as changed -- but stay tuned for an 
announcement next week!

Kaj

Warren wrote:

> I've looked over as much of the information on the new Community vs. 
> Enterprise version stuff as I can find, and I don't see an answer to 
> this question.  Basically, I want to know if the MySQL C API is still 
> dual licensed, under the GPL and the MySQL commercial license.  If so, I 
> don't see how this new model is any different than before, except that 
> the commercial version is now more expensive.
> 
> The practical upshot of the previous licensing scheme, for people that 
> used the MySQL C API, was that you either had to buy a MySQL commercial 
> license, or release your code under the GPL.  That means MySQL could 
> never be "free-of-charge" (quoting today's email from Kaj Arnö) for 
> those people.  For that to happen, the C API must be released under a 
> more liberal license (LGPL at least), or explicitly made public-domain.
> 
> So, has anything substantial changed besides the price of a commercial 
> license?

-- 
Kaj Arnö <kaj@stripped>
MySQL AB, VP Community Relations