[ale] MySql scare tactics?

[Joe Knapka]

"John Wells" <jb at devsea.com> writes:

> Here's an interesting reply from MySql.com sales.  I frankly don't see how
> using it on multiple internal servers constitutes a violation of the GPL. 
> Anyone?

My interpretation of this, and of the original license page (which
I read a couple of days ago before downloading MySQL to install
on my <mumble mumble xp> box), is that:

(1) If your application (which use MySQL) is distributed under the
GPL, you are home free wrt MySQL - distribute it, patch it, give it to
your friend and neighbors (bundled with your app or not), etc. Of
course, you're bound by the terms of the GPL in your actions regarding
MySQL, just as you would be if you were distributing any other GPL app
- you must provide source or info about how to get it, make your
patches available to the community, etc.

(2) If your application is *not* distributed under the GPL, then you
must get a commercial license before doing anything that might be
interpreted as "distribution" of MySQL. It seems to me that they
essentially want to grant a free development license to closed-source
shops, but they want to collect $$ for closed-source runtime licenses.

Cheers,

-- Joe Knapka

> 
> Hi Jb,
> 
> Thank you for your interest in MySQL.  My answers below.
> 
> > -----Original Message-----
> > From: mysql at sourceillustrated.com
> > [mailto:mysql at sourceillustrated.com]
> > Sent: Wednesday, October 08, 2003 7:50 AM
> > To: licensing at mysql.com
> > Subject: MySQL Licensing Question, US, -unknown-
> >
> >
> > The following form was submitted via MySQL.com feedback engine:
> >
> >   Name: JB Wells
> >
> >   Email address: mysql at sourceillustrated.com
> >
> >   Type of interest: for company use
> >
> >   Country: US
> >
> >   Support contract: no
> >
> >   Enter Your Questions, Comments, Feedback or Your Message here:
> >
> >     I'm a little confused on the meaning of "distributing either
> >     externally or internally" on the license page.  If we develop an
> >     application that uses MySql as the backend database and
> > use in on our
> >     internal LAN, do we need to license it commmercially?
> 
> Internal distribution applies to internally distributing/installing more
> than one application.  If you plan to use one installation of MySQL it
> would not be considered distribution and you could use if for free with
> your "internally built application."
> 
> > How would this
> >     be in violation of the GPL?
> 
> If your application (internal or external) is licensed under the terms
> of the GPL, you are allowed to distribute MySQL, also under the GPL, for
> free.
> 
> What do you mean, exactly,
> > by internal
> >     distribution?
> >
> >     Also, if we write an application that expects MySql (like
> > a web app),
> >     but we don't package the database with the application
> > and tell the
> >     customer that they must download and install it, is this
> > violation of
> >     the GPL?
> 
> Again, if your application is licensed under the terms of the GPL you
> can use MySQL for free.  If your application is not licensed under the
> terms of the GPL, commercial non-GPL licenses are necessary.  You will
> need to purchase licenses under this scenario (unless you go GPL),
> please review our licensing examples,
> http://www.mysql.com/products/licensing-examples.html.
> 
> How are you planning to use MySQL?
> 
> Mr. Matt Fredrickson,
> Sales Executive
> MySQL, Inc. - www.mysql.com
> Office: +1 425 390 0154
> Fax: +1 425 663 2001
> 
> MySQL Featured in the Wall Street Journal:
> http://webreprints.djreprints.com/785490482991.html
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale