licensing
License incompatibility between PHP and MariaDB?
<p>I plan to make a simple website with HTML, CSS, PHP and MarìaDB; however, when I read the MariaDB license (GPL V2) I noticed that it is incompatible with the PHP license (this can be seen in the GNU FAQ section).</p>
<p>I have some questions:</p>
<p>If the existence of such license incompatibility means that, for example, when using PHP code to make queries and insertions in MarìaDB, would you be incurring the license incompatibility?</p>
<p>If I were incurring license incompatibility, is there any way I can use PHP and MariaDB without incurring such incompatibility?</p>

<p>You are concerned that your application is somehow a derivative work of MariaDB and therefore subject to the GPL. It's not totally clear to me whether that is the case or not.</p>
<p>But it doesn't matter, because you are not <em>distributing</em> MariaDB itself (or any other part of your application). You're running it on a server which users are connecting to remotely. From MariaDB's <a href="https://mariadb.com/kb/en/licensing-faq/#internal-usage-is-free" rel="nofollow noreferrer">licensing FAQ</a>:</p>
<blockquote>
<h2>Internal usage is free</h2>
<p>The GPL license only affects code that you distribute to other parties.</p>
<p>Internal usage within an organization is totally free and not subject to any conditions. There is no such thing as 'internal distribution' that would restrict the usage of your code by requiring it to be GPLed.</p>
<p>Connecting to a remote service that runs MariaDB (or any other GPL software) in the background is also free.</p>
<p>For internal programs for which you own all the copyright(s), there is essentially no risk in using GPL software. The argument you can use in your defense is that if the software became GPL as part of the distribution, you as the copyright holder could immediately revert your part back to its original copyright. No one has the right to require you to reveal or redistribute your code to the outside of your organization even if you would have distributed it internally linked with GPL software!</p>
<p>If your lawyers are concerned about distributions of software linked with GPL libraries between different legal entities within your organization, you can solve this by distributing your components and the GPL software separately, and have your other entity combining them. You can also switch to use the new LGPL client libraries.</p>
</blockquote>
<p>The use you have described in your question clearly falls into this case, and the presence of this FAQ item clearly demonstrates that the MariaDB developers intended to allow you to do this. The Free Software Foundation (the people who wrote the GPL) agree with this position for both <a href="https://www.gnu.org/licenses/gpl-faq.en.html#InternalDistribution" rel="nofollow noreferrer">unmodified copies</a> and <a href="https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic" rel="nofollow noreferrer">derivative works</a>.</p>
<p>Technically, you don't need a license to &quot;use&quot; a piece of software at all, assuming you have lawfully obtained it. But you're concerned about the possibility of creating a derivative work, for which a license <em>is</em> required. Fortunately, the GPL doesn't care about derivative works so long as they are not distributed.</p>
