<div dir="ltr"><div dir="ltr"><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)">Dear Carlo,</font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)">Thank you for your candid and professional feedback. I understand your concerns regarding license proliferation and the legal nuances of the MIT structure.<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000">To be clear, the reason it's confusing to read is because I have Autism and ADHD, which means that when I tell people stuff in a different way.</font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)"><span class="gmail-Yjhzub" style="font-weight:700">1. Regarding Sublicensing:</span><br>The removal of the sub licensing clause was an attempt at simplification, but I acknowledge that it creates legal ambiguity. I will restore the standard MIT language ("and to permit persons to whom the Software is furnished to do so...") to ensure full legal compatibility and clarity for downstream users.<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)"><span class="gmail-Yjhzub" style="font-weight:700">2. Rationale and Proliferation:</span><br>I hear your invitation not to create "entropy." However, I believe IDCIYMI addresses a specific social gap in 2026. While the legal core is MIT, the <span class="gmail-Yjhzub" style="font-weight:700">"Creator Note"</span> is intended to be a standardized, <span class="gmail-Yjhzub" style="font-weight:700">non-binding (non-legal)</span> field. In current practice, creator intent is scattered across READMEs and NOTICE files in inconsistent ways. IDCIYMI aims to provide a formal, predictable "home" for this aspirational language without altering the legal conditions of the license itself.<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)"><span class="gmail-Yjhzub" style="font-weight:700">3. Clarifying Aspirational Language:</span><br>To avoid the "confusion" you mentioned, I will add a clear prefix to the section stating: <em class="eujQNb" style="font-weight:inherit">"The following Creator Note is for informational purposes only and does not constitute a legal condition of this license."</em><span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)">I am a beginner developer (Bernardo Hora) passionate about modding culture. My goal is to lower the "fear of entry" for new modders who find traditional legal text intimidating. I am open to further adjusting the text to ensure it provides value to the ecosystem without wasting the community's time.<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)">Best regards,<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Y3BBE" style="font-family:"Google Sans",Arial,sans-serif;font-size:16px;line-height:24px;margin:12px 0px 16px"><font color="#000000" style="background-color:rgb(255,255,255)">Bernardo Hora<span class="gmail-txxDge gmail-notranslate" style="visibility: hidden;"><span class="gmail-vKEkVd" style="text-wrap-mode: nowrap;"><button tabindex="0" aria-label="Mostrar links relacionados" class="gmail-rBl3me" style="margin:0px 6px 0px 0px;border-width:initial;border-style:none;border-color:initial;border-radius:10px;height:20px;padding:0px;width:20px;outline:0px"><span class="gmail-wiMplc gmail-ofC0Ud" style="display:inline-block"></span></button></span></span></font></div><div class="gmail-Fsg96" style="font-family:"Google Sans",Arial,sans-serif;font-size:14px"></div><hr class="gmail-j3tEEe" style="height:1px;border-right:0px;border-bottom:0px;border-left:0px;border-top-style:solid;border-top-color:rgb(45,47,53);margin:32px 0px;font-family:"Google Sans",Arial,sans-serif;font-size:14px"><div class="gmail-Fsg96" style="font-family:"Google Sans",Arial,sans-serif;font-size:14px"></div><font color="#000000" style="background-color:rgb(255,255,255)"><br class="gmail-Apple-interchange-newline"></font></div><font color="#000000" style="background-color:rgb(255,255,255)"><br></font><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr"><font color="#000000" style="background-color:rgb(255,255,255)">On Fri, Jan 16, 2026 at 11:10\u202fAM Carlo Piana via License-review <<a href="mailto:license-review@lists.opensource.org">license-review@lists.opensource.org</a>> wrote:<br></font></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font color="#000000" style="background-color:rgb(255,255,255)">Dear Bernardo, <br>
<br>
I notice that the most relevant change to the MIT is the removal of the<br>
<br>
> and to permit persons to whom the Software is furnished to do so, subject to the following conditions<br>
<br>
part. This is the "sublicensing" permission. I am not sure a sublicensing permission is required, since the later users of the software can derive this permission from the original licensing, however they would receive the software, without the need to receive it as an effect of the last distribution. But I don't quite get the rationale of having a new MIT-style license which leaves this implicit. Has a lawyer performed any kind of assessment here? Why?<br>
<br>
Moreover, the addition of aspirational language in legal text, especially without a clear indication that this is not legal text, is IMHO a source of potentially confusing language, and is for sure an invitation to create more proliferation and entropy. Have you have ever tried to perform an OSS compliance audit on any piece of software only to find the umpteenth license to clear for no reason at all, but nonetheless requiring human intervention -- as it is slightly different from allo others? This is a total waste of time and energy and I personally invite all submitters NOT to do that unless there are really compelling legal reasons, or proof of widespread adoption, both totally absent here.<br>
<br>
I take the view that this license does not meet the requirements for being added to the list of officially approved licenses, although per se does not seem to violate any OSD rule, at a cursory evaluation.<br>
<br>
Cheers<br>
<br>
Carlo, in his personal capacity.<br>
<br>
<br>
<br>
<br>
----- Messaggio originale -----<br>
> Da: "PTFS" <<a href="mailto:pfts.offical@gmail.com" target="_blank" style="">pfts.offical@gmail.com</a>><br>
> A: "<a href="mailto:license-review@lists.opensource.org" target="_blank" style="">license-review@lists.opensource.org</a>" <<a href="mailto:license-review@lists.opensource.org" target="_blank" style="">license-review@lists.opensource.org</a>><br>
> Inviato: Sabato, 10 gennaio 2026 14:14:18<br>
> Oggetto: [License-review] License Review: IDCIYMI-1.0 (I Don't Care If You Mod It)<br>
<br>
> Dear OSI License Review Committee,<br>
> I am formally submitting the "I Don't Care If You Mod It" (IDCIYMI) license,<br>
> version 1.0, for official approval as an Open Source license.<br>
<br>
> 1. License Text<br>
<br>
> ========================================================<br>
> IDCIYMI License (I Don't Care If You Mod It)<br>
> Copyright (c) 2026 [Name]<br>
> Permission is hereby granted, free of charge, to any person obtaining a copy<br>
> of this software and associated documentation files (the "Software"), to deal<br>
> in the Software without restriction, including without limitation the rights<br>
> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell<br>
> copies of the Software.<br>
> The only condition is that the above copyright notice and this permission<br>
> notice shall be included in all copies or substantial portions of the Software.<br>
> CREATOR NOTE:<br>
> [Add your note here. For example: "I built this for the community\u2014please mod it<br>
> and share what you create!"]<br>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR<br>
> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,<br>
> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE<br>
> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER<br>
> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,<br>
> OUT OF OR IN CONNECTION WITH THE SOFTWARE.<br>
> ==============================================<br>
<br>
> 1. Rationale The IDCIYMI license fills a unique social gap by standardizing a<br>
> "Creator Note" field within a permissive legal framework. While legally similar<br>
> to MIT, it provides a dedicated space for authors to express their intent and<br>
> encouragement for modifications without introducing legally binding<br>
> restrictions that would violate the OSD. This fosters a culture of remixing and<br>
> open collaboration.<br>
> 2. Open Source Definition (OSD) Affirmation I affirmatively state that this<br>
> license complies with the Open Source Definition. Specifically:<br>
<br>
> *<br>
> OSD 3 (Derived Works): It explicitly permits modifications and sublicensing.<br>
> * OSD 5 & 6 (No Discrimination): The license and its "Creator Note" are<br>
> structured to ensure no groups or fields of endeavor are restricted.<br>
> * OSD 9 (License Must Not Restrict Other Software): It does not restrict other<br>
> software distributed with it.<br>
<br>
> 1.<br>
> Stewardship I, Bernardo Hora, am the steward of this license.<br>
> 2. Existing Usage Since I do not use GitHub, the license and the software using<br>
> it can be found at the following public locations:<br>
<br>
> site : [ <a href="https://idciymi.neocities.org/" rel="noreferrer" target="_blank" style="">https://idciymi.neocities.org/</a> | <a href="https://idciymi.neocities.org/" rel="noreferrer" target="_blank" style="">https://idciymi.neocities.org/</a> ] (the<br>
> site is in wip)<br>
<br>
> _______________________________________________<br>
> The opinions expressed in this email are those of the sender and not necessarily<br>
> those of the Open Source Initiative. Communication from the Open Source<br>
> Initiative will be sent from an <a href="http://opensource.org" rel="noreferrer" target="_blank" style="">opensource.org</a> email address.<br>
<br>
> License-review mailing list<br>
> <a href="mailto:License-review@lists.opensource.org" target="_blank" style="">License-review@lists.opensource.org</a><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank" style="">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
<br>
_______________________________________________<br>
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 <a href="http://opensource.org" rel="noreferrer" target="_blank" style="">opensource.org</a> email address.<br>
<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank" style="">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank" style="">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a></font><br>
</blockquote></div></div>