[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Fwd: MySQL Licensing Question]

From: Glenn A. Thompson <gthompson_at_cdr.net>
Date: 2002-07-08 15:01:23 CEST

Hey:

Back from my rock just for a moment.
I sent some license questions off to MySQL. Here is the response. I'm
not completely comfortable with the response.
I think I check with our lawyers and maybe have them steer me from here.
Overall, I'm not concerned as I will be supporting more than one DB long
term.

gat

Iko Rein wrote:

> Dear Glenn A. Thompson,
>
> > I'm working on a Subversion FS module which uses ODBC.
> >
> > The MySQLODBC licensing is messing with my head a little.
> >
> > Subversion is licensed under the Apache style license.
> >
> > Is there any licensing conflict here?
>
> I guess you mean Subversion, that can be found at
> http://subversion.tigris.org/project_status.html
>
> MySQL and MyODBC are licensed under the GPL, which
> is much stricter license, than the one, that is used with
> Subversion. Our policy has been, that if you just build
> an application, that you link with MyODBC and you
> don't sell that application, you can use MyODBC without
> the fear of inheriting GPL to your application.
>
> > Also, if a end user chose to use MySQL with Subversion in a
> > commercial enterprise::
>
> Using MySQL in a commercial enterprise is not bad
> thing. If they use MySQL under the GPL and/or don't
> distribute MySQL, they can use MySQL for free under
> the GPL license.
>
> > What exposure would they have in terms of them having
> > proprietary code linked into the program linked to Subversion
> > which uses MySQL via ODBC? Shoo a mouthful.
>
> Basic case: MySQL & MyODBC are GPL => Subversion
> should be GPL => their code would be GPL. But if
> you have gotten from us the right to use MySQL &
> MyODBC with Subversion without Subversion becoming
> GPL, then the proprietary code would have no fear
> of inheriting the GPL.
> This is similar to the PHP/Apache/MySQL type of question.
> PHP application (almost) never become GPL, even if they
> would use MySQL. (Only exception is, if you use Zend
> to hide the source code).
>
> > I'm just trying to make sure that the Subversion license is not
> > at risk.
>
> Kind Regards,
> MySQL AB
>
> Iko Rein
> --
> For technical support contracts, goto https://order.mysql.com/?ref=imr
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Iko Rein <iko@mysql.com>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Director of Online Sales
> /_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
> <___/ www.mysql.com

attached mail follows:


Dear Glenn A. Thompson,

> I'm working on a Subversion FS module which uses ODBC.
>
> The MySQLODBC licensing is messing with my head a little.
>
> Subversion is licensed under the Apache style license.
>
> Is there any licensing conflict here?

I guess you mean Subversion, that can be found at
http://subversion.tigris.org/project_status.html

MySQL and MyODBC are licensed under the GPL, which
is much stricter license, than the one, that is used with
Subversion. Our policy has been, that if you just build
an application, that you link with MyODBC and you
don't sell that application, you can use MyODBC without
the fear of inheriting GPL to your application.

> Also, if a end user chose to use MySQL with Subversion in a
> commercial enterprise::

Using MySQL in a commercial enterprise is not bad
thing. If they use MySQL under the GPL and/or don't
distribute MySQL, they can use MySQL for free under
the GPL license.

> What exposure would they have in terms of them having
> proprietary code linked into the program linked to Subversion
> which uses MySQL via ODBC? Shoo a mouthful.

Basic case: MySQL & MyODBC are GPL => Subversion
should be GPL => their code would be GPL. But if
you have gotten from us the right to use MySQL &
MyODBC with Subversion without Subversion becoming
GPL, then the proprietary code would have no fear
of inheriting the GPL.
This is similar to the PHP/Apache/MySQL type of question.
PHP application (almost) never become GPL, even if they
would use MySQL. (Only exception is, if you use Zend
to hide the source code).

> I'm just trying to make sure that the Subversion license is not
> at risk.

Kind Regards,
MySQL AB

Iko Rein

-- 
For technical support contracts, goto https://order.mysql.com/?ref=imr
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Iko Rein <iko@mysql.com>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Director of Online Sales
/_/  /_/\_, /___/\___\_\___/   Helsinki, Finland
       <___/   www.mysql.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 8 15:00:22 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.