<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
</head>
<body>
<p style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none;">
<span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">Yokoi-san,</span></p>
<p style="text-align: left; text-indent: 0px; text-transform: none;"><span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">Thank you for the careful reading. Let me answer from the text
as written.</span></p>
<p style="text-align: left; text-indent: 0px; text-transform: none;"><span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">1) Your reading of the definition is correct: providing the model
as a hosted or API-based service falls within "Distribution" as defined.</span></p>
<p style="text-align: left; text-indent: 0px; text-transform: none;"><span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">2) But note what Paragraph 2.2(a) actually requires: provide a
copy of the License <b>with the Licensed Materials</b>, and retain the notices <b>
as part of the Distribution</b>. In your scenario, no Licensed Materials are transferred to the remote user at all; they only receive Output. Strictly by the text, there is no Licensed Material to attach the License to, and no notices to retain as part of that
distribution. So under the license as written, a provider offering only hosted access owes no Section 2.2(a) obligations to API users.</span></p>
<p style="text-align: left; text-indent: 0px; text-transform: none;"><span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">3) So a provider offering only hosted access owes no Section 2.2(a)
obligations to API users. I would not call this a drafting gap either; our review history points the same way. The output-notice requirement in the earlier MG0 draft was discussed at length in a dedicated thread in March 2025 [1]: it was questioned as "a restriction
or condition on mere use. That would not be open source" [2], analogized to "putting an editor under a license that required any file created with the editor to have an attribution notice" [3], and I agreed at the time that it "somewhat oversteps" [4]. The
requirement was later removed. Any new wording about providing license information on a service page should therefore be drafted as the method of satisfying attribution, not as a condition on use.</span></p>
<p style="text-align: left; text-indent: 0px; text-transform: none; margin-top: 26px;">
<span style="font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 15px; color: rgb(29, 29, 43);">Best,<br>
<b>Moming Duan</b></span></p>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
<br>
</div>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
[1] <a href="https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005698.html" data-outlook-id="7031538b-a257-48ff-b28a-7cccb42aadd9">
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005698.html</a></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
<br>
[2] <a href="https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005704.html" data-outlook-id="400131e7-8f9a-4496-a08e-b1538deaed0d">
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005704.html</a></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
<br>
[3] <a href="https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005711.html" data-outlook-id="e4128177-f833-4690-8b6c-cccb687cbf79">
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005711.html</a></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
<br>
[4] <a href="https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005718.html" data-outlook-id="40babf8c-ebee-42ad-8887-1b6798a94b9e">
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2025-March/005718.html</a></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; text-transform: none; margin-top: 1em; margin-bottom: 1em; font-family: -apple-system, "Segoe UI", Helvetica, Arial, sans-serif; font-size: 13px; color: rgb(85, 85, 85);">
<br>
</div>
<div id="mail-editor-reference-message-container">
<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 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 横井雄太 <yuta.yokoi.r@gmail.com><br>
<b>Date: </b>Thursday, September 3, 2026 at 23:54<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>
<div id="mail-editor-reference-message-body">
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
</div>
<p class="ms-outlook-mobile-reference-message skipProofing">I have one question about how the final MG-BY-2.0 text is intended to operate when Distribution consists solely of remote access.</p>
<p class="ms-outlook-mobile-reference-message skipProofing">The definition of “Distribution” expressly includes:</p>
<p class="ms-outlook-mobile-reference-message skipProofing">“providing the Licensed Materials or any part thereof as a hosted service or remotely accessible service, such as API-based access or web access.”</p>
<p class="ms-outlook-mobile-reference-message skipProofing">Section 2.2(a), in turn, provides that if a licensee Distributes Licensed Materials or Derivative Materials, the licensee must, among other things:</p>
<ol start="1">
<li>provide a copy of the License with the Licensed Materials or Derivative Materials; and</li><li>retain, as part of the Distribution, existing copyright, attribution, and author-identification notices.</li></ol>
<p class="ms-outlook-mobile-reference-message skipProofing">I would like to understand precisely how those conditions are intended to be performed where the Distribution consists only of hosted or remotely accessible use.</p>
<p class="ms-outlook-mobile-reference-message skipProofing">For example, suppose a provider operates an MG-BY-2.0-licensed model entirely on its own servers and exposes only an inference API or web interface. The remote user can interact with the model and
receive Output, but receives no copy of the model weights, checkpoints, architecture files, Complementary Materials, or other underlying Licensed Materials.</p>
<p class="ms-outlook-mobile-reference-message skipProofing">My reading is that this still falls within the definition of “Distribution,” because hosted and remotely accessible services are expressly included.</p>
<p class="ms-outlook-mobile-reference-message skipProofing">If that reading is correct, could the steward clarify the following?</p>
<ol start="1">
<li>
<p class="ms-outlook-mobile-reference-message skipProofing" role="presentation">Does providing API-based or web-based access to the hosted model trigger the Section 2.2(a) conditions even though no copy of the underlying Licensed Materials is transferred to
the remote user?</p>
</li><li>
<p class="ms-outlook-mobile-reference-message skipProofing" role="presentation">If so, what constitutes compliance with the requirement to provide a copy of the License “with the Licensed Materials” and to retain attribution notices “as part of the Distribution”
in that remote-access context? For example, would making the License and applicable attribution notices clearly and persistently available through the service interface or accompanying API documentation satisfy those requirements?</p>
</li><li>
<p class="ms-outlook-mobile-reference-message skipProofing" role="presentation">More generally, how should the express inclusion of hosted and remotely accessible services in the definition of “Distribution” be reconciled with Section 2.2(a)’s language concerning
materials and notices provided “with” or “as part of” the Distribution where no underlying model artifact is actually delivered to the user?</p>
</li></ol>
<p class="ms-outlook-mobile-reference-message skipProofing">I am not suggesting that remote access should or should not be treated as Distribution, nor am I suggesting a particular form of compliance. My question is limited to how the current text is intended
to operate in a scenario that the definition expressly includes.</p>
<p class="ms-outlook-mobile-reference-message skipProofing">I think clarification would be useful for downstream users because the submission materials specifically identify remote-access scenarios, such as chatbot use, as one of the situations the ModelGo
licenses are designed to address. A user deploying MG-BY-2.0 solely as a hosted service should therefore be able to determine from the license what actions satisfy the attribution and license-notice requirements in that expressly contemplated mode of Distribution.</p>
</div>
</div>
</body>
</html>