<div dir="auto">Dear McCoy and the License Review Committee,<div dir="auto">\u200bThank you for your patience as I refine this submission. I am providing the updated project context and the formal declarations requested.</div><div dir="auto">\u200b1. Projects Utilizing the License</div><div dir="auto">The license is primarily intended for a specialized framework built on React (by Meta). The goal is to provide a "Zero-Attribution" alternative to the MIT license that ensures long-term maintenance and compatibility for React-based UI components.</div><div dir="auto">\u200b2. Legal Analysis of the Affirmative Obligation</div><div dir="auto">Regarding the "Duty to Repair" in a non-attribution context:</div><div dir="auto">\u200bContractual Condition: The "Maintenance Obligation" is a condition precedent to the license grant. While the user is not required to provide attribution, the Author's right to distribute the software is contingent upon their commitment to the "Duty to Repair."</div><div dir="auto">\u200bBinding Nature: If the maintainer fails to provide "best efforts" to address defects (such as breaking changes in the underlying React framework), they are in breach of the license conditions.</div><div dir="auto">\u200b3. Identity of Steward and Submitter</div><div dir="auto">I, Vicentte Felipe, am the submitter and the License Steward.</div><div dir="auto">\u200bContact: <a href="mailto:vicenttefelipe097@gmail.com">vicenttefelipe097@gmail.com</a></div><div dir="auto">\u200b4. External Approvals & Identifiers</div><div dir="auto">\u200bNo prior approvals from FSF, Debian, or Fedora exist.</div><div dir="auto">\u200bNo SPDX or ScanCode identifiers exist yet.</div><div dir="auto">\u200b5. License Text (Fixed)</div><div dir="auto">I have attached the fixed LICENSE.txt to this email for the permanent record.</div><div dir="auto">\u200bBest regards,</div><div dir="auto">\u200bVicentte Felipe</div><div dir="auto">Software Developer & Architect</div><div dir="auto"><a href="https://github.com/Vicenttefelipe097/Modified-0BSD-License">https://github.com/Vicenttefelipe097/Modified-0BSD-License</a></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">El mar, 17 de mar de 2026, 12:42, McCoy Smith <mccoy@lexpan.law> escribió:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<p>You do not appear to have answered the following questions per
the license review guidelines:<br>
<br>
* Submit a copy of the license as an attachment in simple text
format.</p>
<p> This is requested because repositories can change and we need
to have a fixed text that all reviewers can review. </p>
<p>* Identify what projects are already using the license.</p>
<p> You have not indicated any projects that are using, or are
proposing to use, this license.</p>
<p>* Provide the identity and contact details of the license
steward, if known, and of the submitter. The OSI will try to get
in touch with the license steward if the license submitter is not
the steward.</p>
<p> If you are the steward, you should identify yourself as such
(since the license has your (C) notice on it I assume you are the
steward, but you should state so affirmatively).</p>
<p>* Provide any additional information that the submitter believes
would be helpful for license review. For example, approval of the
license by Debian, the FSF or the Fedora Project would be relevant
to the review process.</p>
<p> If no other approvals exist, you should state so.</p>
<p> * If any exist, provide the unique identifier by other projects,
like SPDX or ScanCode.</p>
<p> If no identifiers exist, you should state so.</p>
<p>* Describe any legal review the license has been through,
including whether it was drafted by a lawyer.</p>
<p> You have listed a "legal analysis" but have not indicated if
any lawyer was involved in that analysis or the drafting of the
license. In particular, I think there needs to be some description
how the affirmative obligation may be binding on the recipient
under the terms of this agreement. </p>
<div>On 3/17/2026 8:24 AM, Vicentte Felipe
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Dear License Review Committee,
<div dir="auto">\u200bPursuant to the OSI License Review Process, I
am providing the formal responses required for the review of
the Modified 0BSD License.</div>
<div dir="auto">\u200b1. Support for the Open Source Definition
(OSD):</div>
<div dir="auto">The license complies with all 10 criteria of the
OSD. It allows for free redistribution, includes source code,
allows for derived works, and does not discriminate against
any persons or fields of endeavor.</div>
<div dir="auto">\u200b2. Unique Benefits:</div>
<div dir="auto">Currently, most permissive licenses (MIT, BSD,
0BSD) include a total disclaimer of warranty ("AS-IS"). This
license provides a middle ground for developers who wish to
offer a high degree of freedom (Zero Attribution) while
legally committing to the quality and maintenance of the code.
It provides "Accountable Open Source."</div>
<div dir="auto">\u200b3. Proliferation Category:</div>
<div dir="auto">This is a Special Purpose License. It is not
intended to replace the MIT or 0BSD licenses for all users,
but rather to serve projects where the developer wants to
provide a "Maintenance Mandate" as a core feature of the
software's distribution.</div>
<div dir="auto">\u200b4. Comparison to Similar Licenses:</div>
<div dir="auto">\u200bVs. 0BSD: It is identical in its grant of
rights and removal of attribution, but it removes the "AS-IS"
clause and replaces it with the "Maintenance Obligation."</div>
<div dir="auto">\u200bVs. TAPR Open Hardware License: Like some
hardware licenses, it focuses on the "Duty to Repair" or
maintain, but adapted for software.</div>
<div dir="auto">\u200b5. Legal Analysis:</div>
<div dir="auto">The "Maintenance Obligation" is structured as a
Condition of the License. If the maintainer or distributor
fails to fulfill the duty to repair, the license grant is
technically revoked, ensuring that "dead" or "unmaintained"
forks cannot claim to be part of the supported ecosystem.</div>
<div dir="auto">\u200b6. Formal License Text:</div>
<div dir="auto">Modified 0BSD License (Maintenance-Required)</div>
<div dir="auto">Copyright (c) 2026 Vicentte Felipe</div>
<div dir="auto"><br>
</div>
<div dir="auto">Permission to use, copy, modify, and/or
distribute this software for any</div>
<div dir="auto">purpose with or without fee is hereby granted.</div>
<div dir="auto"><br>
</div>
<div dir="auto">THE MAINTENANCE OBLIGATION:</div>
<div dir="auto">Unlike the standard 0BSD license, this software
is NOT provided "as-is." </div>
<div dir="auto">The Original Author(s) and/or those who
explicitly claim to provide a supported version of this
software accept an affirmative obligation to:</div>
<div dir="auto">\u200bReview and address reported technical defects.</div>
<div dir="auto"><br>
</div>
<div dir="auto">LIMITATION OF LIABILITY:</div>
<div dir="auto">THE AUTHOR(S) SHALL NOT BE LIABLE FOR ANY
SPECIAL, DIRECT, INDIRECT, OR </div>
<div dir="auto">CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
RESULTING FROM LOSS OF USE, </div>
<div dir="auto">DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER </div>
<div dir="auto">TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR </div>
<div dir="auto">PERFORMANCE OF THIS SOFTWARE. THE REMEDY IS
LIMITED TO THE MAINTENANCE </div>
<div dir="auto">OBLIGATIONS STATED ABOVE.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">El mar, 17 de mar de 2026,
11:00, McCoy Smith <a href="mailto:mccoy@lexpan.law" target="_blank" rel="noreferrer"><mccoy@lexpan.law></a> escribió:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vicentte:<br>
<br>
In order for this license to be considered for approval, you
need to <br>
answer all the questions set forth in the process for
approval, found <br>
here: <a href="https://opensource.org/licenses/review-process" rel="noreferrer noreferrer noreferrer" target="_blank">https://opensource.org/licenses/review-process</a><br>
<br>
If you want this license to be considered for approval, please
follow <br>
the process as indicated on OSI's website.<br>
<br>
On 3/17/2026 3:56 AM, Vicentte Felipe wrote:<br>
> Dear OSI License Review Committee,<br>
> \u200bI am formally submitting the Modified 0BSD License for
review and <br>
> approval against the Open Source Definition (OSD).<br>
> \u200bFollowing previous feedback regarding trademark
concerns, I have <br>
> renamed and refactored the license. It is now based on
the established <br>
> BSD Zero Clause License (0BSD) framework, but with a
specific <br>
> modification to address developer accountability.<br>
> \u200bSubmission Details:<br>
> \u200bLicense Name: Modified 0BSD License
(Maintenance-Required)<br>
> \u200bVersion: 1.0<br>
> \u200bOfficial Repository: <br>
> <a href="https://github.com/Vicenttefelipe097/Modified-0BSD-License" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/Vicenttefelipe097/Modified-0BSD-License</a><br>
> \u200bRationale: To provide a "Zero-Attribution" permissive
license that <br>
> replaces the standard "AS-IS" disclaimer with a "Duty to
Repair." This <br>
> ensures that users can rely on a commitment to
maintenance while <br>
> enjoying the freedom of a 0BSD-style grant.<br>
> \u200bLicense Text:<br>
> Modified 0BSD License (Maintenance-Required)<br>
> Copyright (c) 2026 Vicentte Felipe<br>
><br>
> Permission to use, copy, modify, and/or distribute this
software for any<br>
> purpose with or without fee is hereby granted.<br>
><br>
> THE MAINTENANCE OBLIGATION (THE VICENTTE DUTY):<br>
> Unlike the standard 0BSD license, this software is NOT
provided "as-is."<br>
> The Author(s) and/or Distributor(s) accept an affirmative
obligation to:<br>
> 1. Review and address reported technical defects and
bugs.<br>
> 2. Use best efforts to provide fixes for issues that
impair the <br>
> software\u2019s<br>
> intended functionality.<br>
><br>
> LIMITATION OF LIABILITY:<br>
> THE AUTHOR(S) SHALL NOT BE LIABLE FOR ANY SPECIAL,
DIRECT, INDIRECT, OR<br>
> CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF <br>
> USE,<br>
> DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER<br>
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
USE OR<br>
> PERFORMANCE OF THIS SOFTWARE. THE REMEDY IS LIMITED TO
THE MAINTENANCE<br>
> OBLIGATIONS STATED ABOVE.<br>
> I believe this modification maintains the spirit of open
source while <br>
> providing a modern framework for professional
stewardship. I look <br>
> forward to the committee\u2019s feedback.<br>
> \u200bBest regards,<br>
> \u200bVicentte Felipe Software Developer & Architect<br>
> <a href="https://github.com/Vicenttefelipe097" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/Vicenttefelipe097</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 noreferrer noreferrer" target="_blank">opensource.org</a> email address.<br>
><br>
> License-review mailing list<br>
> <a href="mailto:License-review@lists.opensource.org" rel="noreferrer noreferrer" target="_blank">License-review@lists.opensource.org</a><br>
> <a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer noreferrer noreferrer" target="_blank">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 noreferrer noreferrer" target="_blank">opensource.org</a> email address.<br>
<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" rel="noreferrer noreferrer" target="_blank">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<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 <a href="http://opensource.org" target="_blank" rel="noreferrer">opensource.org</a> email address.
License-review mailing list
<a href="mailto:License-review@lists.opensource.org" target="_blank" rel="noreferrer">License-review@lists.opensource.org</a>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" target="_blank" rel="noreferrer">http://lists.opensource.org/mailman/listinfo/license-review_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. Communication from the Open Source Initiative will be sent from an <a href="http://opensource.org" rel="noreferrer noreferrer" target="_blank">opensource.org</a> email address.<br>
<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank" rel="noreferrer">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
</blockquote></div>