<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi McCoy,<div><br></div><div><br></div><div>Thanks for your reply. The MG-*-OS License requires providing a copy of the code but does not enforce a specific license for it. My lawyer opposed adding such enforcement due to potential incompatibility between the code license and our MG license.</div><div><br></div><div>BTW, from my understanding, the current OSAID applies to AI systems, correct? Is it a requirement for open-source model licenses to comply with it? For example, should an open-source model license include terms ensuring that its code and data are also governed by an OSI-approved license?</div><div><br></div><div><br></div><div>Best,</div><div>Moming</div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 11 Feb 2025, at 1:23 AM, McCoy Smith <mccoy@lexpan.law> wrote:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div><p>you definitely should not submit any license that doesn't comply
with the OSD, like anything that is -NC.</p><p>wrt the -OS license, if it allows for only open weights but not
open code, that probably violates OSD too.<br>
</p>
<div class="moz-cite-prefix">On 2/9/2025 11:15 PM, "D 莫名 (dewitt)"
wrote:<br>
</div>
<blockquote type="cite" cite="mid:44E07E8A-4C94-498D-B438-BB84B62C7961@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Dear All,
<div>
<div><br>
</div>
<div><br>
</div>
<div>I am a researcher at National University of Singapore (NUS)
working on AI licensing. Recently, I collaborated with legal
experts to draft a public-use, model-specific license aimed at
promoting more standardized model publishing. As you may know,
there are far fewer model licenses than software licenses for
general model publishing, leading many to use OSS and Creative
Commons (CC) licenses instead. However, these licenses do not
fully address ML-specific behaviors, potentially causing legal
uncertainties (we have conducted research on this issue). </div>
<div><br>
</div>
<div>To address this gap, we drafted ModelGo Licenses, a
CC-style licensing framework designed specifically for models.
There are nine variations of ModelGo (MG) Licenses, such as
MG-BY, MG-BY-RAI, and MG-BY-OS, similar to the structure of CC
licenses. Currently, we are preparing to enter the OSI license
review process and start a discussion, as suggested.</div>
<div><br>
</div>
<div>1) <span style="caret-color: rgb(0, 0, 0);">My
first question is: </span>Should I submit all variations?
Since we have nine licenses that share a large portion of
their terms and conditions, I wonder if submitting them all is
necessary.</div>
<div><br>
</div>
<div>2) Additionally, some licenses, such as MG-BY-NC (which
restricts commercial use of the model), clearly do not comply
with the OSD. Should I submit them as complementary materials
instead?</div>
<div><br>
</div>
<div>3) Lastly, while I attempted to align MG-BY-OS (where "OS"
stands for "Open Source") with OSI’s Open AI definition by
requiring that complementary code be licensed under an
OSI-approved license, our lawyers opposed this due to concerns
about terms incompatibility. Currently, the MG-BY-OS license
only mandates open-sourcing the model weights, related code,
and scripts (excluding data). I would appreciate any advice on
this point.</div>
</div>
<div><br>
</div>
<div>I participated in the drafting and amendment of ModelGo
Licenses and am very willing to discuss any details about them.
Please feel free to reach out for discussion. Thanks, everyone!</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="caret-color: rgb(0, 0, 0);">Text
version of MG-BY at <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>
<div><br>
</div>
<div>All licenses at:</div>
<div>NUS ModelGo Licenses Website: <a href="https://ids.nus.edu.sg/modelgo.html" moz-do-not-send="true" class="moz-txt-link-freetext">https://ids.nus.edu.sg/modelgo.html</a></div>
<div>ModelGo Licenses and FAQ (published by me more info here): <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><br>
</div>
<div><br>
</div>
<div>Best,</div>
<div>Moming Duan, </div>
<div>Institute of Data Science, NUS</div>
<div><br>
</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. Official statements by the Open Source Initiative will be sent from an opensource.org email address.
License-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-discuss@lists.opensource.org">License-discuss@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address.<br><br>License-discuss mailing list<br>License-discuss@lists.opensource.org<br>http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org<br></div></blockquote></div><br></div></body></html>