Re: MySQL JDBC driver - implications for non-GPLed apps
From: Mark Matthews (mark_at_mysql.com)
Date: 05/14/04
- Next message: Chris Smith: "Re: MySQl-database"
- Previous message: Mladen Adamovic: "Re: universal JDBC replicating proxy"
- In reply to: Chris Smith: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Next in thread: Alex Molochnikov: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Reply: Alex Molochnikov: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Reply: Carl Rosenberger: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 14 May 2004 09:06:04 -0500 To: Chris Smith <cdsmith@twu.net>
Chris Smith wrote:
[snip]
>> I think the final answer is really simple, as another poster already
>> suggested: if the vendor makes it too problematic for other parties to
>> support their product, then... well... so long. They are not the only game
>> in town.
>
> Yes. It's a shame, though, that MySQL has gained so much, in terms of
> free development work *and* good name, by licensing under the GPL, and
> now they intend to threaten and browbeat everyone out of using the code
> in a way they are entitled to use it. As someone who has contributed to
> and led several open-source software projects, that really gets under my
> skin. I know I wouldn't want a bunch of greedy executives taking
> advantage of me like that. (Who knows? For all I know, there may be
> some of my code in MySQL, copied from other GPL projects in a way that
> would be completely fine and admirable if they intended to actually give
> people the rights promised by the GPL).
Chris,
Just to clear something up...We don't 'lift' code from GPL products. We
require clear IP to all of the code in our products so that we can also
license it commercially, so in fact almost all of it is written by MySQL
employees.
I would also venture to say that MySQL AB is far from a bunch of 'greedy
executives', the company is mostly full of technical people who care
very passionately about open source.
Considering one of our company values is "Make superior database
software available to all", and given our actions (because they speak
louder than words), which include making _every_single_ product we have
available under the GPL, including technology that was expensive to
create and/or acquire such as MySQL Cluster, as well has having _no_
feature differences between our open source and commercial software, I
find it hard to paint us with that brush. However, if that's how you see
us, I'd like to help rectify that image (feel free to contact me
personally if you want to discuss it further).
What we do get from the open source community is connectivity pieces to
'esoteric' languages that wouldn't be commercially viable to support,
open source applications that support MySQL and a vibrant community of
testers, authors and community support. We are _very_ thankful for this
support from the community, which is why we do make everything we create
available under an open source license.
However, what we're really trying to get at with the licensing (and
still working on getting there, but it takes careful consideration), is
the notion of 'quid-pro-quo'...i.e. if your application is open source,
then MySQL is open source (in fact, there's a GPL license exception for
MySQL software that allows you to use it with OSI-certified licenses
that are historically incompatible with the GPL)...if your application
is closed source, then MySQL is closed source.
That last bit is really not much different than other commercial
vendors, if you take a look at Alex's issue and how he's distributing
connectivity components for his report generator, you will see that in
almost all of those client licenses that the end user is _eventually_
required to _purchase_ a license for the database server software to run
it in anything but test environments. The connectivity doesn't come for
'free', because legally you can't use it unless you're using a license
for the server that was _paid_ for, which ultimately pays for the
connectivity bits as well.
MySQL is working on an ISV/VAR option for the client libraries for
comemrcial licensees, if you have input on how you think this should
work, please let us know.
You could also investigate using a dual license model such as MySQL's,
SleepyCat's or TrollTech's, where you _could_ use MySQL under the GPL
and commercial licenses when you were generating revenue with commercial
sales.
-Mark
-- Mr. Mark Matthews MySQL AB, Software Development Manager, J2EE and Windows Platforms Office: +1 708 332 0507 www.mysql.com MySQL Guide to Lower TCO http://www.mysql.com/it-resources/white-papers/tco.php
- Next message: Chris Smith: "Re: MySQl-database"
- Previous message: Mladen Adamovic: "Re: universal JDBC replicating proxy"
- In reply to: Chris Smith: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Next in thread: Alex Molochnikov: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Reply: Alex Molochnikov: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Reply: Carl Rosenberger: "Re: MySQL JDBC driver - implications for non-GPLed apps"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
