Can I bundle Apache 2.0 licensed components in a GPL 3 licensed project?
<p>I am creating a project that I would like to open source and license under the GPL 3 License. The project will come with a bundled version of an open source component which is licensed under the Apache 2.0 license.</p>

<p>Can I bundle Apache 2.0 licensed components in a GPL 3 licensed project?</p>

<p>I would also be interested in an explanation on why the answer is yes or no.</p>

<p>The Free Software Foundation considers that the <a href="https://www.gnu.org/licenses/license-list.html#apache2" rel="noreferrer">Apache 2.0 license is compatible with the GPL 3.0</a>:</p>
<blockquote>
<p>This is a free software license, compatible with version 3 of the GNU GPL.</p>
</blockquote>
<p>But not compatible with the GPL 2.0, though:</p>
<blockquote>
<p>Please note that this license is not compatible with GPL version 2, because it has some requirements that are not in that GPL version. These include certain patent termination and indemnification provisions. The patent termination provision is a good thing, which is why we recommend the Apache 2.0 license for substantial programs over other lax permissive licenses.</p>
</blockquote>
<p><strong>But what does it mean when the FSF says a license is &quot;<a href="https://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean" rel="noreferrer">compatible with the GPL</a>?&quot;</strong></p>
<blockquote>
<p>It means that the other license and the GNU GPL are compatible; you can combine code released under the other license with code released under the GNU GPL in one larger program.</p>
<p>All GNU GPL versions permit such combinations privately; they also permit distribution of such combinations provided the combination is released under the same GNU GPL version. The other license is compatible with the GPL if it permits this too.</p>
<p>GPLv3 is compatible with more licenses than GPLv2: it allows you to make combinations with code that has specific kinds of additional requirements that are not in GPLv3 itself. Section 7 has more information about this, including the list of additional requirements that are permitted.</p>
</blockquote>
<p>So what can you make of this? The FSF considers these two licenses compatible and it also means that when you combine code under these two licenses, the effective obligations that will apply are these of the Apache and GPL combined, including source code redistribution.</p>
<p>But why are the compatible? Is the fact that the FSF says so enough?</p>
<p>We can check what the Apache Software Foundation <a href="https://www.apache.org/licenses/GPL-compatibility.html" rel="noreferrer">says on the topic</a>:</p>
<blockquote>
<p>The Free Software Foundation considers the Apache License, Version 2.0 to be a free software license, compatible with version 3 of the GPL. The Software Freedom Law Center provides practical advice for developers about including permissively licensed source.</p>
<p>Apache 2 software can therefore be included in GPLv3 projects, because the GPLv3 license accepts our software into GPLv3 works.</p>
</blockquote>
<p>So irrespective of the deeper why, they tend to agree and as they are the authors of the respective licenses, this carries some weight.</p>
<p>But wait, this is not true the other way around as the ASF goes on:</p>
<blockquote>
<p>However, GPLv3 software cannot be included in Apache projects. The licenses are incompatible in one direction only, and it is a result of ASF's licensing philosophy and the GPLv3 authors' interpretation of copyright law.</p>
</blockquote>
<p>So in a nutshell, the FSF considers that the terms of the Apache license are compatible with the copyleft terms of the GPL 3.0. The ASF agrees, but the copyleft terms of the GPL 3.0 are not compatible with the permissive terms of the Apache 2.0: a combination of the two would have to be copyleft.</p>

software licensing open-source-software gpl