MySQL Licensing в Коммерческом использовании веб-приложения В спящем режиме [закрытый]

Do not make business decisions based on legal advice you get on the internet -- including mine.

My understanding is that if you tell your customer that they are responsible for downloading and installing MySQL and the JDBC connector, you can get around the GPL license terms.

If you distribute GPL software with your application, your software implicitly uses that license too. You would be obligated to allow your customer access to your source code. including the rights to modify it and distribute it themselves.

You could choose as your default RDBMS another popular open-source RDBMS with a more permissive license, such as:

• PostgreSQL (BSD license)
• SQLite (public domain)
• Firebird (InterBase Public License, based on the Mozilla Public License)

Re your question in comment: Confluence is actually not open source, it's a commercial product. They do make source available to commercial license holders, but this doesn't qualify as open-source per the OSI definition.

Confluence uses JDBC, a non-RDBMS-specific API defined by Sun Microsystems. Confluence distributes with a lightweight Java database called HSQL or HypersonicHSQL, which uses a license like the New BSD License. If the customer wants to use Confluence with MySQL he has to install it himself.

See http://confluence.atlassian.com/display/DOC/Database+Setup+For+MySQL where the setup documentation tells you to go download and install MySQL and MySQL Connector/J.

The key to why this works for a non-open-source product like Confluence is that their product doesn't necessarily need to use MySQL, it can use a different JDBC driver (and in fact does so, by default). Since there's no dependency on using MySQL specifically, Confluence doesn't need to comply with the terms of GPL.

If you have other questions about GPL, the GPL FAQ is probably the best place for you to start, instead of StackOverflow. See http://www.gnu.org/licenses/gpl-faq.html