Re^2: Protecting our work

Actually, it's if you "bundle" MySQL in with your non-OSS application, then you trigger the commerical side of MySQL's dual-license and you have to puchase a commerical license. However, merely the use of MySQL on a customer's machine doesn't trigger anything. The customer has chosen to install MySQL as part of their system and then chosen to use your application. You haven't bundled anything. The same goes for the web application you're hosting on your machine and other people pay you to use it.

In other words, unless you're distributing a Win32 app for the masses, the commerical side of MySQL's license is usually irrelevant.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re^2: Protecting our work

Replies are listed 'Best First'.
Re^3: Protecting our work by salva (Canon) on Aug 29, 2005 at 10:54 UTC
No, an application that links to GPL code (as last versions of MySQL client library are) can only be distributed as GPL'd.	[reply]
Re^4: Protecting our work by deliria (Chaplain) on Aug 29, 2005 at 12:56 UTC
Here's an interesting interpretation from Sleepycat (BerkeleyDB). While it might not be 100% aplicable to Mysql's license, the definition of the term application would be key here. Do I have to pay for a Berkeley DB license to use it in my Perl or Python scripts? No, you may use the Berkeley DB open source license at no cost. The Berkeley DB open source license requires that software that uses Berkeley DB be freely redistributable. In the case of Perl or Python, that software is Perl or Python, and not your scripts. Any scripts you write are your property, including scripts that make use of Berkeley DB. None of the Perl, Python or Berkeley DB licenses place any restrictions on what you may do with them.	[reply]
Re^5: Protecting our work by salva (Canon) on Aug 29, 2005 at 13:52 UTC
On the GPL FAQ: If a programming language interpreter is released under the GPL, does that mean programs written to be interpreted by it must be under GPL-compatible licenses?.	[reply]
Re^6: Protecting our work by deliria (Chaplain) on Aug 29, 2005 at 18:42 UTC
Re^4: Protecting our work by dragonchild (Archbishop) on Aug 30, 2005 at 15:40 UTC
From http://www.mysql.com/company/legal/licensing/: The Commercial License, which allows you to provide commercial software licenses to your customers or distribute MySQL-based applications. This is for organizations that do not want to release the source code for their applications as open source / free software; in other words they do not want to comply with the GNU General Public License (GPL). (emphasis mine) For those developing open source applications, the Open Source License allows you to offer your software under an open source / free software license to all who wish to use, modify, and distribute it freely. The Open Source License allows you to use the software at no charge under the condition that if you use MySQL in an application you redistribute, the complete source code for your application must be available and freely redistributable under reasonable conditions. MySQL AB bases its interpretation of the GPL on the Free Software Foundation's Frequently Asked Questions. Looks like we're both slightly in error. (I based my conclusions on the class I took a year ago.) My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]