Re: [openstack-dev] mysql/mysql-python license contamination into openstack?

2014-06-14 Thread Eoghan Glynn 


 On Thu Jun 12 14:13:05 2014, Chris Friesen wrote:
  Hi,
 
  I'm looking for the community viewpoint on whether there is any chance
  of license contamination between mysql and nova.  I realize that
  lawyers would need to be involved for a proper ruling, but I'm curious
  about the view of the developers on the list.
 
  Suppose someone creates a modified openstack and wishes to sell it to
  others.  They want to keep their changes private.  They also want to
  use the mysql database.
 
  The concern is this:
 
  nova is apache licensed
  sqlalchemy is MIT licensed
  mysql-python (aka mysqldb1) is GPLv2 licensed
  mysql is GPLv2 licensed
 
 
 
  The concern is that since nova/sqlalchemy/mysql-python are all
  essentially linked together, an argument could be made that the work
  as a whole is a derivative work of mysql-python, and thus all the
  source code must be made available to anyone using the binary.
 
  Does this argument have any merit?
 
 the GPL is excepted in the case of MySQL and other MySQL products
 released by Oracle (can you imagine such a sentence being
 written.), see
 http://www.mysql.com/about/legal/licensing/foss-exception/.   If
 MySQL-Python itself were an issue, OpenStack could switch to another
 MySQL library, such as MySQL Connector/Python which is now MySQL's
 official Python driver:
 http://dev.mysql.com/doc/connector-python/en/index.html

Usual IANAL caveats ...

But do these concerns about license contamination from the DB service,
via the client libraries, have any relevance to the prior discussion
about MongoDB licensing?

Substituting:

  s/mysql is GPLv2/mongodb is AGPLv3/
  s/sqlalchemy is MIT licensed/pymongo is Apache licensed/

and noting the MongoDB Inc promise about database and client library
separateness.

If there is some relevance, then some of the conclusions to the prior
legal discussion may be useful to recall:

  http://lists.openstack.org/pipermail/legal-discuss/2014-March/000189.html

Cheers,
Eoghan

  Has anyone tested any of the mysql DBAPIs with more permissive licenses?
 
 I just mentioned other MySQL drivers the other day; MySQL
 Connector/Python, OurSQL and pymysql are well tested within SQLAlchemy
 and these drivers generally pass all tests.   There's some concern over
 compatibility with eventlet, however, I can't speak to that just yet.
 
 
  Chris
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] mysql/mysql-python license contamination into openstack?

2014-06-13 Thread Chris Friesen 

On 06/12/2014 01:30 PM, Mike Bayer wrote:


the GPL is excepted in the case of MySQL and other MySQL products
released by Oracle (can you imagine such a sentence being
written.), see
http://www.mysql.com/about/legal/licensing/foss-exception/.


Okay, good start.  mysql itself is out of the picture.



If
MySQL-Python itself were an issue, OpenStack could switch to another
MySQL library, such as MySQL Connector/Python which is now MySQL's
official Python driver:
http://dev.mysql.com/doc/connector-python/en/index.html


It seems like mysql-python could be an issue given that it's licensed GPLv2.


Has anyone tested any of the mysql DBAPIs with more permissive licenses?


I just mentioned other MySQL drivers the other day; MySQL
Connector/Python, OurSQL and pymysql are well tested within SQLAlchemy
and these drivers generally pass all tests.   There's some concern over
compatibility with eventlet, however, I can't speak to that just yet.


Okay, so they're not really tested with OpenStack then?

Chris


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] mysql/mysql-python license contamination into openstack?

2014-06-12 Thread Jay Pipes 

On 06/12/2014 02:13 PM, Chris Friesen wrote:

Hi,

I'm looking for the community viewpoint on whether there is any chance
of license contamination between mysql and nova.  I realize that lawyers
would need to be involved for a proper ruling, but I'm curious about the
view of the developers on the list.

Suppose someone creates a modified openstack and wishes to sell it to
others.  They want to keep their changes private.  They also want to use
the mysql database.


IANAL and all that...but...

The problem is not in their closed product *using* MySQL. The problem is 
in the *distribution* of the product. If the product is distributed with 
MySQL packaged with the product (and thereby the product is distributing 
the MySQL source or binaries), that is not permitted by the GPL.


Best,
-jay


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev