<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Moming,</p>
<p>As I read it, there is only one thing that applies to Output,
which is in the Limitation of Liability. But does the fact that
you mention it in the first place lead to a negative implication
that you haven't granted the necessary rights to create Output?
With software it's been a fairly bright line that any output isn't
subject matter of the license unless it's a derivative work. Here,
though, you have created ambiguity about the legal status of the
output by mentioning it and also made the license much more
complicated. </p>
<p>In my view it's not worth including Output at all in the license.
The only liability you <i>might</i> be avoiding is from the person
creating the output. The Limitation on Liability won't be a
defense to any claims from copyright owners, or those whose loved
one harmed themselves because the model encouraged them to do so,
or criminal liability. So I don't think it's worth the trade-off,
although I wouldn't reject the license for that reason.</p>
<p>Pam</p>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
4641 Post St.<br>
Unit 4316<br>
El Dorado Hills, CA 95762<br>
+1 919-800-8033<br>
pamela@chesteklegal<br>
<a class="moz-txt-link-abbreviated" href="http://www.chesteklegal.com">www.chesteklegal.com</a><br>
<br>
<br>
</div>
<div class="moz-cite-prefix">On 12/8/2025 6:57 PM, Moming Duan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3760E516-7839-446B-9797-2A24ABF97F52@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Dear OSI License Review Community,
<div><br>
</div>
<div><br>
</div>
<div>As suggested, I am starting this new thread to submit the
updated MG0-2.0 and MG-BY-2.0 <span
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">licenses</span> that
address the comments from the second resubmission. The major
modification is the exclusion of models created through
distillation from the definition of Derivative Materials, along
with two improvements suggested by McCoy. I have also provided
word-diff comparisons with the previous versions. Please feel
free to share any comments.</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Word-diff:</div>
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">MG0: <a
href="https://www.diffchecker.com/f8OumPRF/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.diffchecker.com/f8OumPRF/</a></div>
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">MG-BY: <a
href="https://www.diffchecker.com/jVBWA9WF/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.diffchecker.com/jVBWA9WF/</a></div>
</div>
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div><br>
</div>
<div>Best,</div>
<div>Moming</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div><font color="#ff13ff"><span
style="caret-color: rgb(0, 0, 0);">\u2014\u2014\u2014\u2014\u2014\u2014 </span><span
style="caret-color: rgb(0, 0, 0);">License </span><span
style="caret-color: rgb(0, 0, 0);">Introduction
(MG0-2.0)</span></font></div>
<div><font color="#ff13ff"><br>
</font></div>
<div><font color="#ff13ff"><b>License Name</b>:<span
class="Apple-tab-span" style="white-space: pre;"> </span><span
style="caret-color: rgb(0, 0, 0);">ModelGo Zero License</span></font></div>
<div><span style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff"><b>Version</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>2.0</font></span></div>
<div><font color="#ff13ff"><b>Short Identifier: <span
class="Apple-tab-span" style="white-space: pre;"> </span></b>MG0-2.0</font></div>
<div><font color="#ff13ff"><b
style="caret-color: rgb(0, 0, 0);">Copyleft:</b><span
class="Apple-tab-span"
style="caret-color: rgb(0, 0, 0); font-weight: bold; white-space: pre;"> </span><span
style="caret-color: rgb(0, 0, 0);">No</span></font></div>
<div><font color="#ff13ff"><b>Legacy or New</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>New
License</font></div>
<div><font color="#ff13ff"><b>Drafted By Lawyer</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>Yes, Rajah
& Tann Singapore LLP</font></div>
<div><font color="#ff13ff"><b>Approved or <span
style="caret-color: rgb(0, 0, 0);">Used</span> by
Projects</b>: <span class="Apple-tab-span"
style="white-space: pre;"> </span>No</font></div>
<div><br>
</div>
<div><b>License URL</b>:<span class="Apple-tab-span"
style="white-space: pre;"> </span><a
href="https://ids.nus.edu.sg/modelgo-mg0.html"
moz-do-not-send="true" class="moz-txt-link-freetext">https://ids.nus.edu.sg/modelgo-mg0.html</a></div>
<div><b>Introduction and Video</b>:<span
class="Apple-tab-span" style="white-space: pre;"> </span><a
href="https://www.modelgo.li/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.modelgo.li/</a></div>
<div><br>
</div>
<div><b>Overview</b>:</div>
<div><br>
</div>
<div>ModelGo Zero License Version 2.0 (MG0-2.0) is a new
license designed for publishing models (typically neural
networks like Llama2, DeepSeek). It is one of the variants
in the ModelGo License family. MG0-2.0 is the most
permissive license in the ModelGo family.</div>
<div><br>
</div>
<div><b>Complies with OSD:</b></div>
<div><b><br>
</b></div>
<div>OSD 3 Derived Work<font color="#ff13ff">s \u2014 MG0-2.0 <span
style="caret-color: rgb(0, 0, 0);"> </span><span
style="caret-color: rgb(0, 0, 0);">Clause 2.1 (a) grants
copyright and patent rights to create derivatives.</span></font></div>
<div><font color="#ff13ff">OSD 5 and OSD 6 \u2014 No discrimination
clause is included in MG0-2.0.</font></div>
<div><font color="#ff13ff">OSD 9 License Must Not Restrict
Other Software \u2014 No such restriction is included in
MG0-2.0.</font></div>
<div><br>
</div>
<div><b>The Gap to Fill:</b></div>
<div>Model sharing is very common on the web, with over 1.4
million models currently listed on Hugging Face (<a
href="https://huggingface.co/models"
moz-do-not-send="true" class="moz-txt-link-freetext">https://huggingface.co/models</a>).
However, most of these models are not properly licensed.
When publishing their models, developers typically choose
from three main options (as seen in the model license tags
on the Hugging Face website):</div>
<div><br>
</div>
<div>
<ul class="MailOutline">
<li>OSS licenses, e.g., Apache-2.0, MIT</li>
<li>Open responsible AI licenses (OpenRAILs),
e.g., CreativeML-OpenRAIL-M, OpenRAIL++</li>
<li>Proprietary Licenses, e.g., Llama2, Llama3</li>
</ul>
</div>
<div><br>
</div>
<div>However, not all licenses are well-suited for model
publishing.</div>
<div><br>
</div>
<div><b>Why not use OSS licenses? </b></div>
<div>Traditional OSS licenses lack clear definitions regarding
machine learning concepts, such as Models, Output, and
Derivatives created through knowledge transfer. This
ambiguity can result in certain ML activities (e.g.,
Distillation, Mix-of-Expert) being beyond the control of the
model owner.</div>
<div><br>
</div>
<div><b>Why not use OpenRAILs? </b></div>
<div>Recently, Responsible AI Licenses (<a
href="https://www.licenses.ai/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.licenses.ai/</a>)
have been widely advocated to govern AI technologies, aiming
to restrict unlawful and unethical uses of models. While I
acknowledge the growing need for such governance, these
copyleft-style restrictions do not comply with the OSD and
may cause incompatibility with licenses like GPL-3.0.
Another concern is that these behavioral restrictions may
proliferate within the AI model ecosystem, increasing the
risk of license breaches.</div>
<div><br>
</div>
<div><b style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">Why not use Llama2 or Llama3 Licenses?</font></b></div>
<div><font color="#ff13ff">These licenses are proprietary
licenses that are not reusable. Furthermo</font>re, they
include exclusive terms such as "You will not use the Llama
Materials or any output or results of the Llama Materials to
improve any other large language model" and copyleft-style
behavioral restrictions.</div>
<div><br>
</div>
<div>In fact, the dilemma in current model publishing is the
lack of a general-purpose license for model developers.
Additionally, since no single license meets diverse model
publishing needs, some developers resort to using CC
licenses with different elements. However, CC licenses are
ill-suited for this purpose as they do not grant patent
rights. This motivated the drafting of ModelGo License
family, which provides different licensing elements similar
to CC but specifically designed for model publishing.</div>
<div><br>
</div>
<div><b>Comparison with Existing OSI-Approved Licenses:</b></div>
<div>Since I could not find an OSI-approved model license, I
can only compare MG0-2.0 with one similar OSS license \u2014
Apache-2.0</div>
<div>
<div><font color="#ff13ff"><br>
</font></div>
<div>
<li style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">MG0-2.0 defines licensed materials and
derivative works differently from Apache-2.0,
tailoring them to models.</font></li>
<li style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">MG0-2.0 can govern the remote access
(e.g., chatbot) scenario.</font></li>
<li style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">MG0-2.0 does not require retaining
attribution or stating modifications when
redistributing derivatives.</font></li>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div><font color="#ff13ff"><span
style="caret-color: rgb(0, 0, 0);">\u2014\u2014\u2014\u2014\u2014\u2014 </span><span
style="caret-color: rgb(0, 0, 0);">License </span><span
style="caret-color: rgb(0, 0, 0);">Introduction
(MG-BY-2.0)</span></font></div>
<div><b><br>
</b></div>
<div><font color="#ff13ff"><b>License Name</b>:<span
class="Apple-tab-span" style="white-space: pre;"> </span><span
style="caret-color: rgb(0, 0, 0);">ModelGo </span>Attribution<span
style="caret-color: rgb(0, 0, 0);"> License</span></font></div>
<div><span style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff"><b>Version</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>2.0</font></span></div>
<div><font color="#ff13ff"><b>Short Identifier: <span
class="Apple-tab-span" style="white-space: pre;"> </span></b>MG-BY-2.0</font></div>
<div><font color="#ff13ff"><b
style="caret-color: rgb(0, 0, 0);">Copyleft:</b><span
class="Apple-tab-span"
style="caret-color: rgb(0, 0, 0); font-weight: bold; white-space: pre;"> </span><span
style="caret-color: rgb(0, 0, 0);">No</span></font></div>
<div><font color="#ff13ff"><b>Legacy or New</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>New
License</font></div>
<div><font color="#ff13ff"><b>Drafted By Lawyer</b>: <span
class="Apple-tab-span" style="white-space: pre;"> </span>Yes, Rajah
& Tann Singapore LLP</font></div>
<div><font color="#ff13ff"><b>Approved or <span
style="caret-color: rgb(0, 0, 0);">Used</span> by
Projects</b>: <span class="Apple-tab-span"
style="white-space: pre;"> </span>No</font></div>
<div><br>
</div>
<div><b>License URL</b>:<span class="Apple-tab-span"
style="white-space: pre;"> </span><a
href="https://ids.nus.edu.sg/modelgo-mg-by.html"
moz-do-not-send="true" class="moz-txt-link-freetext">https://ids.nus.edu.sg/modelgo-mg-by.html</a></div>
<div><b>Introduction and Video</b>:<span
class="Apple-tab-span" style="white-space: pre;"> </span><a
href="https://www.modelgo.li/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.modelgo.li/</a></div>
<div><br>
</div>
<div><b>Overview</b>:</div>
<div><br>
</div>
<div>ModelGo Attribution License Version 2.0 (MG-BY-2.0) is a
new license designed for publishing models (typically neural
networks like Llama2, DeepSeek). It is one of the variants
in the ModelGo License family. MG-BY-2.0 is the a permissive
license in the ModelGo family, requiring that the original
license <font color="#ff0000">and attribution</font> be
provided when distributing the original Licensed Materials
or Derivative Materia<font color="#ff13ff">ls (<span
style="caret-color: rgb(0, 0, 0);">Licensed Materials
and </span><span style="caret-color: rgb(0, 0, 0);">Derivative
Materials are</span><span
style="caret-color: rgb(0, 0, 0);"> </span>defined</font>
in Clause 1). <font color="#ff0000">A statement of
modification is required, if applicable.</font></div>
<div><font color="#ff0000">(Red content represents the
differences from MG0-2.0 license)</font></div>
<div><br>
</div>
<div><b>Complies with OSD:</b></div>
<div><b><br>
</b></div>
<div>OSD 3 Derived Works \u2014 M<font color="#ff13ff">G-BY-2.0 <span
style="caret-color: rgb(0, 0, 0);"> </span><span
style="caret-color: rgb(0, 0, 0);">Clause 2.1 (a) grants
copyright and patent rights to create derivatives.</span></font></div>
<div>OSD 5 and OSD 6 \u2014 No discrimination clause is included in
MG-BY-2.0.</div>
<div>OSD 9 License Must Not Restrict Other Software \u2014 No such
restriction is included in MG-BY-2.0.</div>
<div><br>
</div>
<div><b>The Gap to Fill:</b></div>
<div>Model sharing is very common on the web, with over 1.4
million models currently listed on Hugging Face (<a
href="https://huggingface.co/models"
moz-do-not-send="true" class="moz-txt-link-freetext">https://huggingface.co/models</a>).
However, most of these models are not properly licensed.
When publishing their models, developers typically choose
from three main options (as seen in the model license tags
on the Hugging Face website):</div>
<div><br>
</div>
<div>
<ul class="MailOutline">
<li>OSS licenses, e.g., Apache-2.0, MIT</li>
<li>Open responsible AI licenses (OpenRAILs),
e.g., CreativeML-OpenRAIL-M, OpenRAIL++</li>
<li>Proprietary Licenses, e.g., Llama2, Llama3</li>
</ul>
</div>
<div><br>
</div>
<div>However, not all licenses are well-suited for model
publishing.</div>
<div><br>
</div>
<div><b>Why not use OSS licenses? </b></div>
<div>Traditional OSS licenses lack clear definitions regarding
machine learning concepts, such as Models, Output, and
Derivatives created through knowledge transfer. This
ambiguity can result in certain ML activities (e.g.,
Distillation, Mix-of-Expert) being beyond the control of the
model owner.</div>
<div><br>
</div>
<div><b>Why not use OpenRAILs? </b></div>
<div>Recently, Responsible AI Licenses (<a
href="https://www.licenses.ai/" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.licenses.ai/</a>)
have been widely advocated to govern AI technologies, aiming
to restrict unlawful and unethical uses of models. While I
acknowledge the growing need for such governance, these
copyleft-style restrictions do not comply with the OSD and
may cause incompatibility with licenses like GPL-3.0.
Another concern is that these behavioral restrictions may
proliferate within the AI model ecosystem, increasing the
risk of license breaches.</div>
<div><br>
</div>
<div><b style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">Why not use Llama2 or Llama3 Licenses?</font></b></div>
<div><font color="#ff13ff">These licenses are proprietary
licenses that are not reusable. Furthe</font>rmore, they
include exclusive terms such as "You will not use the Llama
Materials or any output or results of the Llama Materials to
improve any other large language model" and copyleft-style
behavioral restrictions.</div>
<div><br>
</div>
<div>In fact, the dilemma in current model publishing is the
lack of a general-purpose license for model developers.
Additionally, since no single license meets diverse model
publishing needs, some developers resort to using CC
licenses with different elements. However, CC licenses are
ill-suited for this purpose as they do not grant patent
rights. This motivated the drafting of ModelGo License
family, which provides different licensing elements similar
to CC but specifically designed for model publishing.</div>
<div><br>
</div>
<div><b>Co<font color="#ff13ff">mparison with Existing
OSI-Approved Licenses:</font></b></div>
<div><font color="#ff13ff">Since I could not find an
OSI-approved model license, I can only compare MG-BY-2.0
with one similar OSS license \u2014 Apache-2.0</font></div>
<div>
<div><font color="#ff13ff"><br>
</font></div>
<div>
<li style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">MG-BY-2.0 defines licensed materials
and derivative works differently from Apache-2.0,
tailoring them to models.</font></li>
<li style="caret-color: rgb(0, 0, 0);"><font
color="#ff13ff">MG-BY-2.0 can govern the remote access
(e.g., chatbot) scenario.</font></li>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
</body>
</html>