<div dir="ltr"><div><font size="4">Dear OSI License Review Committee,</font></div><div>I am formally submitting the BOS Public License v1.3 for review and OSI approval.</div><div>The BOS Public License is a permissive, file-based attribution license based structurally on the standard MIT License, but with specific, explicit terms regarding upstream repository tracking and credit preservation.</div><div><br></div><div><font size="4">RATIONALE & COMPARISON:</font></div><div>While the standard MIT License requires the preservation of copyright notices, it does not explicitly guarantee that downstream forks preserve a pointer back to the immediate upstream source code repository or an immutable developer credits file.</div><div>To prevent legal traps associated with network uptime or platform-dependent API structures, Version 1.3 utilizes a static, technology-neutral file mechanism (UPSTREAM.txt and CREDITS.txt) similar in intent to the NOTICE file mechanics found in the Apache 2.0 license.</div><div>Downstream modifiers are strictly responsible for preserving the physical text files themselves, meaning temporary network outages or broken URLs do not impact legal compliance or introduce shifting liability.
Below is the full text of the license for your evaluation.</div><div><br></div><div>Thank you for your time and consideration, </div><div>Luis Harz</div><div><font size="4"><br></font></div><div><font size="4">----------------------------------------------------------------------</font></div><div><b>THE BOS PUBLIC LICENSE (Better Open Source)</b><br>Version 1.3 Based on the MIT License with custom attribution terms<br>Copyright (c) 2026 [Your Name or Organization]<br><br>Permission is hereby granted, free of charge, to any person obtaining a copy<br>of this software and associated documentation files (the \u201cSoftware\u201d), 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, and to permit persons to whom the Software is<br>furnished to do so, subject to the following conditions:<br><br>The above copyright notice, this permission notice, and the additional terms<br>below shall be included in all copies, forks, or substantial portions of the Software.<br><br>ADDITIONAL TERMS:<br>(Note: The additional terms below apply strictly to public Source Code distribution and repositories, not to compiled binaries or object code.)<br><br>1. Upstream Identification: If the Software includes an UPSTREAM.txt file at <br> its root containing a URL or reference to the upstream repository, this file <br> must be preserved without removal or alteration in all public distributions <br> of the source code. The downstream modifier is not legally responsible for <br> the ongoing availability, validity, or uptime of the URL specified within <br> the file, only for the preservation of the text file itself. Downstream <br> modifiers are permitted to append their own repository location to this file.<br><br>2. Preservation of Credits: If the Software contains a CREDITS.txt file, <br> existing names and credits within this file must be preserved without removal <br> or alteration in all forks, modifications, or republished versions of the <br> Software. You are permitted to add new credits or names (for yourself or <br> other contributors) to the file.<br><br>THE SOFTWARE IS PROVIDED \u201cAS IS\u201d, 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 OR THE USE OR OTHER DEALINGS IN<br>THE SOFTWARE.</div></div>