Does AGPL apply to products created by the software, or just the software?
<p>I'm a 3D modeler by trade, and in the past I've used some software to create a base mesh for humanoid renders. I'm seeing now that, while it used to be AGPL and CC0, it's now entirely AGPL, and by some mechanism which I do not fully understand this seems to apply to products and meshes created with it.</p>
<p>That is, if I produce a model while using this software, I am required to release the model, and any software dependent on the model (say, a game or a web app), under the same license. This feels extraordinarily aggressive.</p>
<p>This is very strange to me. It feels like a paintbrush manufacturer demanding royalties on all paintings done with their brush. Additionally, when AGPL was created, it was apparently to close a gap in GPLv3 which allowed companies to alter software on a server and open it to the public via a web interface; which was phrased loosely enough to potentially apply to all products created by the program.</p>
<p>While I'm historically a big fan of GPL-created works and feel that they have done wonders for the whole of the software and multimedia community, this AGPL oddity is a total deal-breaker for the software-in-question. I'm no longer even entirely certain about my rights to my videos. What is the nature of this reach? Do I need to make my application AGPL simply because I used an AGPL-produced resource in it? And, perhaps most importantly, <em>has this ever been enforced in a court of law, or could it be in the United States?</em></p>

<p>OK, seems I was right to begin with, but after building some work with this I had to be sure. The problem seems to step from a lot of not-lawyers overinterpreting the reach and applicability of copyright law, which, with a few asides, is the full extent of the AGPL. Additionally, the software is not based in an English-speaking country, which may have thrown the interpreted meaning of &quot;derivative product&quot;, as opposed to simply &quot;product&quot;.</p>
<p>The AGPL is indeed in almost all ways the same as the GPL version 3; in fact you can see this by <code>diff</code>ing the two documents. The only extension of the GPLv3 made for AGPL applies to software being run on a server. While it is indeed possible to include code in the final files, which might, in theory, constitute a significant portion of this program, that does not happen.</p>
<p>The AGPL is apparently also meant almost exclusively for software, though the wording does include the ambiguous phrase &quot;and other products&quot;; this concerned me as it felt as though it might apply to the resources created by the work. It, broadly speaking, does not.</p>
<p>So, I've got nothing to worry about--unless I was distributing derivative software, which would be an entirely different question and subject to this.</p>

<p>The AGPL and GPL can be applied to output, since the output is a derivative of data licensed under the (A)GPL. Making a model with MB-Lab is not the same as writing a word document from scratch. The model is not conjured from the end-user's input. The sliders are illusions of user input and control; the programmer, not you, decided what happens when a slider is moved. To claim that a MB-Lab character model belongs to you because you moved a slider is similar to claiming that a Skyrim or Fire Emblem Awakening character model belongs to you because you moved a slider.</p>
<p>This is why <a href="https://spdx.org/licenses/exceptions-index.html" rel="nofollow noreferrer">exceptions to the AGPL and GPL exist</a>. One fitting exception is <a href="https://www.gnu.org/licenses/autoconf-exception-3.0.html" rel="nofollow noreferrer">Autoconf-exception-3.0</a>:</p>
<blockquote>
<p>AUTOCONF CONFIGURE SCRIPT EXCEPTION</p>
<p>Version 3.0, 18 August 2009</p>
<p>Copyright (C) 2009 Free Software Foundation, Inc. <a href="https://fsf.org/" rel="nofollow noreferrer">https://fsf.org/</a></p>
<p>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.</p>
<p>This Exception is an additional permission under section 7 of the GNU General Public License, version 3 (&quot;GPLv3&quot;).  It applies to a given file that bears a notice placed by the copyright holder of the file stating that the file is governed by GPLv3 along with this Exception.</p>
<p>The purpose of this Exception is to allow distribution of Autoconf's typical output under terms of the recipient's choice (including proprietary).</p>
<ol start="0">
<li>Definitions</li>
</ol>
<p>&quot;Covered Code&quot; is the source or object code of a version of Autoconf that is a covered work under this License.</p>
<p>&quot;Normally Copied Code&quot; for a version of Autoconf means all parts of its Covered Code which that version can copy from its code (i.e., not from its input file) into its minimally verbose, non-debugging and non-tracing output.</p>
<p>&quot;Ineligible Code&quot; is Covered Code that is not Normally Copied Code.</p>
<ol>
<li>Grant of Additional Permission.</li>
</ol>
<p>You have permission to propagate output of Autoconf, even if such propagation would otherwise violate the terms of GPLv3.  However, if by modifying Autoconf you cause any Ineligible Code of the version you received to become Normally Copied Code of your modified version, then you void this Exception for the resulting covered work.  If you convey that resulting covered work, you must remove this Exception in accordance with the second paragraph of Section 7 of GPLv3.</p>
<ol start="2">
<li>No Weakening of Autoconf Copyleft.</li>
</ol>
<p>The availability of this Exception does not imply any general presumption that third-party software is unaffected by the copyleft requirements of the license of Autoconf.</p>
</blockquote>
<p>This exception permits the end-user to own and choose the license of the output by making an explicit distinction between &quot;Ineligible Code&quot; and &quot;Normally Copied Code&quot; and spelling out what you may and may not do with each. However, without an explicit exception, such output would be automatically be covered by GPL. If it were otherwise, as you claim, then such exceptions wouldn't be necessary. To put it another way, the need to explicitly list an exception indicates that the rule and its associated problems do indeed exist, i.e. <em>the exception proves the rule</em>.</p>
<p>Another exception is the the <a href="https://github.com/makehumancommunity/makehuman/blob/master/LICENSE.md" rel="nofollow noreferrer">MakeHuman's license exception</a>: Unlike ML-Lab, they explicitly licensed their data under CC0 so that the end-user can choose the license for the output derived from that data. I have to wonder if the original question mistakenly conflated MakeHuman and MB-Lab together: MakeHuman uses <a href="https://github.com/makehumancommunity/makehuman/blob/master/LICENSE.md" rel="nofollow noreferrer">a AGPL+CC0 combo</a>, while MB-Lab uses <a href="https://github.com/animate1978/MB-Lab/blob/master/license.txt" rel="nofollow noreferrer">a GPL+AGPL combo</a>.</p>

<p>I suspect this might depend on the program you're refering to. At least with MB-Labs, the meshes themselves are considered under gnu3/agpl according to the license faq - they seem to use agpl and gnu3  interchangably, which doesn't help matters, but i think thry changed from gnu3 to agpl once it was designed. Unfortunately, the licence basically made the program impossible for me to use for anything other then diy drawing references. :(</p>
<p>if I am wrong, i would LOVE to know that! So far mb has been the best free human design program i've found.</p>
<p>quote from the official website for MB-Labs</p>
<blockquote>
<p>All data files released in the MB-Lab package, including all the meshes and data &gt;contained in .blend files or in any other 3d file format, all the images and all the &gt;json files are released under GNU Affero General Public License 3.</p>
</blockquote>

open-source-software gpl