<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Pam, Josh, and everyone,</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks again for all the feedback over the past year, it's been really helpful.</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i><br>
</i></div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b><i>A quick follow-up on two things </i></b></div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b><i><br>
</i></b></div>
<ul data-editing-info="{"applyListStyleFromLevel":false,"unorderedStyleType":2}" style="margin-top: 0px; margin-bottom: 0px;">
<li style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px; list-style-type: "- ";">
<div role="presentation"><b><i>On the review status:</i></b> </div>
</li></ul>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The board minutes from January 16 mentioned that ModelGo licenses were still in discussions. Just wanted to check in, what's the latest major concern about these two licenses? Happy to work on addressing it : )</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<ul data-editing-info="{"applyListStyleFromLevel":false,"unorderedStyleType":2}" style="margin-top: 0px; margin-bottom: 0px;">
<li style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin-top: 0px; margin-bottom: 0px; list-style-type: "- ";">
<div role="presentation"><b><i>On Pam's point about Output in the Limitation of Liability:</i></b></div>
</li></ul>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Just to follow up on that, with AI agents now generating and auto-executing code, the risk around model output has gotten pretty real, so having Output explicitly covered in the disclaimer and limitation of liability seems like a meaningful protection. And
I noticed that both Meta (Llama) and Google (Gemma) also mention Output in their warranty disclaimers, which might be for similar reasons. So I'm leaning toward keeping it as is, but happy to hear if others feel differently.</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best,</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Moming</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
</div>
<div style="padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>License-review <license-review-bounces@lists.opensource.org> on behalf of Pamela Chestek <pamela@chesteklegal.com><br>
<b>Date: </b>Monday, December 15, 2025 at 20:52<br>
<b>To: </b>license-review@lists.opensource.org <license-review@lists.opensource.org><br>
<b>Subject: </b>Re: [License-review] [3rd Resubmission] ModelGo Zero License (MG0-2.0) AND ModelGo Attribution License (MG-BY-2.0)<br>
<br>
</div>
</div>
<p class="ms-outlook-mobile-reference-message skipProofing">Hi Moming,</p>
<p class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing">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 href="http://www.chesteklegal.com" class="moz-txt-link-abbreviated" data-outlook-id="33f319f7-3c41-4ca0-9d66-b67cfe307fde">www.chesteklegal.com</a><br>
<br>
<br>
</div>
<div class="moz-cite-prefix">On 12/8/2025 6:57 PM, Moming Duan wrote:</div>
<blockquote>
<div class="ms-outlook-mobile-reference-message skipProofing">Dear OSI License Review Community,</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">As suggested, I am starting this new thread to submit the updated MG0-2.0 and MG-BY-2.0
<span style="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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(0, 0, 0);">
Word-diff:</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(0, 0, 0);">
MG0: <a href="https://www.diffchecker.com/f8OumPRF/" class="moz-txt-link-freetext" data-outlook-id="445195c5-a451-4382-9b73-feb11e93d9fe">
https://www.diffchecker.com/f8OumPRF/</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(0, 0, 0);">
MG-BY: <a href="https://www.diffchecker.com/jVBWA9WF/" class="moz-txt-link-freetext" data-outlook-id="0cc82dfe-aa1d-4f4c-9c00-1afb1c1ebae6">
https://www.diffchecker.com/jVBWA9WF/</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; color: rgb(0, 0, 0);">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">Best,</div>
<div class="ms-outlook-mobile-reference-message skipProofing">Moming</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<blockquote>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
License Introduction (MG0-2.0)</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; color: rgb(255, 19, 255);">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>License Name</b>: ModelGo Zero License</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Version</b>: 2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Short Identifier: </b>MG0-2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Copyleft: </b>No</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Legacy or New</b>: New License</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Drafted By Lawyer</b>: Yes, Rajah & Tann Singapore LLP</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Approved or Used by Projects</b>: No</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>License URL</b>:
<a href="https://ids.nus.edu.sg/modelgo-mg0.html" class="moz-txt-link-freetext" data-outlook-id="32605168-362e-4f9a-81e0-259a659267d9">
https://ids.nus.edu.sg/modelgo-mg0.html</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Introduction and Video</b>:
<a href="https://www.modelgo.li/" class="moz-txt-link-freetext" data-outlook-id="e31f91fc-02f4-4dc6-906a-8f6531013cdd">
https://www.modelgo.li/</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Overview</b>:</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Complies with OSD:</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<b><br>
</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">OSD 3 Derived Work<span style="color: rgb(255, 19, 255);">s MG0-2.0 Clause 2.1 (a) grants copyright and patent rights to create derivatives.</span></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
OSD 5 and OSD 6 No discrimination clause is included in MG0-2.0.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
OSD 9 License Must Not Restrict Other Software No such restriction is included in MG0-2.0.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>The Gap to Fill:</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">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" class="moz-txt-link-freetext" data-outlook-id="8ffb9369-026d-43d8-90ea-6655516f4eea">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<ul>
<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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">However, not all licenses are well-suited for model publishing.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Why not use OSS licenses? </b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Why not use OpenRAILs? </b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">Recently, Responsible AI Licenses (<a href="https://www.licenses.ai/" class="moz-txt-link-freetext" data-outlook-id="055b511f-2537-4697-8f2a-14a2ba8d015e">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Why not use Llama2 or Llama3 Licenses?</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing"><span style="color: rgb(255, 19, 255);">These licenses are proprietary licenses that are not reusable. Furthermo</span>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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Comparison with Existing OSI-Approved Licenses:</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">Since I could not find an OSI-approved model license, I can only compare MG0-2.0 with one similar OSS license Apache-2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; color: rgb(255, 19, 255);">
<br>
</div>
<li style=""><span style="color: rgb(255, 19, 255);">MG0-2.0 defines licensed materials and derivative works differently from Apache-2.0, tailoring them to models.</span></li><li style=""><span style="color: rgb(255, 19, 255);">MG0-2.0 can govern the remote access (e.g., chatbot) scenario.</span></li><li style=""><span style="color: rgb(255, 19, 255);">MG0-2.0 does not require retaining attribution or stating modifications when redistributing derivatives.</span></li></blockquote>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<blockquote>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
License Introduction (MG-BY-2.0)</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<b><br>
</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>License Name</b>: ModelGo Attribution License</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Version</b>: 2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Short Identifier: </b>MG-BY-2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Copyleft: </b>No</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Legacy or New</b>: New License</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Drafted By Lawyer</b>: Yes, Rajah & Tann Singapore LLP</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Approved or Used by Projects</b>: No</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>License URL</b>:
<a href="https://ids.nus.edu.sg/modelgo-mg-by.html" class="moz-txt-link-freetext" data-outlook-id="f063c435-2aee-461b-bbae-6728e97e19b8">
https://ids.nus.edu.sg/modelgo-mg-by.html</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Introduction and Video</b>:
<a href="https://www.modelgo.li/" class="moz-txt-link-freetext" data-outlook-id="5f859274-e9e2-4999-8187-8e46ac1acdae">
https://www.modelgo.li/</a></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Overview</b>:</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">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
<span style="color: rgb(255, 0, 0);">and attribution</span> be provided when distributing the original Licensed Materials or Derivative Materia<span style="color: rgb(255, 19, 255);">ls (Licensed Materials and Derivative Materials are defined</span> in Clause
1). <span style="color: rgb(255, 0, 0);">A statement of modification is required, if applicable.</span></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 0, 0);">
(Red content represents the differences from MG0-2.0 license)</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Complies with OSD:</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<b><br>
</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">OSD 3 Derived Works M<span style="color: rgb(255, 19, 255);">G-BY-2.0 Clause 2.1 (a) grants copyright and patent rights to create derivatives.</span></div>
<div class="ms-outlook-mobile-reference-message skipProofing">OSD 5 and OSD 6 No discrimination clause is included in MG-BY-2.0.</div>
<div class="ms-outlook-mobile-reference-message skipProofing">OSD 9 License Must Not Restrict Other Software No such restriction is included in MG-BY-2.0.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>The Gap to Fill:</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">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" class="moz-txt-link-freetext" data-outlook-id="eb030f70-707a-4f30-a869-b5b205617052">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<ul>
<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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">However, not all licenses are well-suited for model publishing.</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Why not use OSS licenses? </b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Why not use OpenRAILs? </b></div>
<div class="ms-outlook-mobile-reference-message skipProofing">Recently, Responsible AI Licenses (<a href="https://www.licenses.ai/" class="moz-txt-link-freetext" data-outlook-id="a31d11c9-eded-4437-9ffb-cf76814b6feb">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
<b>Why not use Llama2 or Llama3 Licenses?</b></div>
<div class="ms-outlook-mobile-reference-message skipProofing"><span style="color: rgb(255, 19, 255);">These licenses are proprietary licenses that are not reusable. Furthe</span>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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing">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 class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<div class="ms-outlook-mobile-reference-message skipProofing"><b>Co</b><span style="color: rgb(255, 19, 255);"><b>mparison with Existing OSI-Approved Licenses:</b></span></div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="color: rgb(255, 19, 255);">
Since I could not find an OSI-approved model license, I can only compare MG-BY-2.0 with one similar OSS license Apache-2.0</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; color: rgb(255, 19, 255);">
<br>
</div>
<li style=""><span style="color: rgb(255, 19, 255);">MG-BY-2.0 defines licensed materials and derivative works differently from Apache-2.0, tailoring them to models.</span></li><li style=""><span style="color: rgb(255, 19, 255);">MG-BY-2.0 can govern the remote access (e.g., chatbot) scenario.</span></li></blockquote>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
</div>
<pre><div 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 href="mailto:License-review@lists.opensource.org" class="moz-txt-link-abbreviated" data-outlook-id="85ae7af9-c416-4484-a3e3-47172556f2ea">License-review@lists.opensource.org</a>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" class="moz-txt-link-freetext" data-outlook-id="d1c54d8f-3005-41f9-bedb-6d6624b6a8f6">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</div></pre>
</blockquote>
</div>
</body>
</html>