[License-review] For Approval: The BOS Public License v1.0
Pamela Chestek
pamela at chesteklegal.com
Fri Jul 24 02:30:14 UTC 2026
Please provide all the information as required on this page,
https://opensource.org/licenses/review-process, and in particular do not
skip "Describe any legal review the license has been through, including
whether it was drafted by a lawyer."
Pamela S. Chestek
Chestek Legal
4641 Post St.
Unit 4316
El Dorado Hills, CA 95762
+1 919-800-8033
pamela at chesteklegal.com
www.chesteklegal.com
On 7/22/2026 2:44 PM, Harz Tronics wrote:
> Hello OSI Team,
> I would like to submit the BOS Public License v1.0 for OSI approval
> under the License Review Process.
>
> == Introduction & Rationale ==
>
> The BOS Public License is a permissive license based on the standard
> MIT License, enhanced with custom attribution terms designed to
> address a common issue in modern open-source development: lost
> attribution and broken traceability in public repository forks.
>
>
> In the modern Git ecosystem, public forks and republications on
> platforms like GitHub or GitLab often strip context away from the
> original repository. The BOS License aims to increase fairness and
> transparency without imposing restrictions on software usage,
> modification, or commercial exploitation.
>
> == Summary of Additional Terms ==
>
> The license adds two specific conditions:
> Original Project Link: Any fork, web-hosted repository, or public
> republication of this Software (such as on GitHub, GitLab, or similar
> platforms) must contain a clearly visible and accessible link back to
> the original repository in its primary documentation (e.g., the README
> file or main project description).
>
> Note on scope: This requirement applies strictly to public code
> distribution and public repository forks; it does not apply to
> private, internal, offline, or execution-only use.
>
>
> Preservation of Credits: If the original repository contains a
> CREDITS.txt file, this file must be preserved completely unaltered and
> included in all forks, modifications, or republished versions of the
> Software.
>
> == Distinction from Existing Licenses ==
>
> Unlike standard MIT or BSD licenses, the BOS License explicitly
> ensures a backlink to the primary repository for public online
> distributions, while carefully avoiding restrictions on non-public,
> offline, or internal usage.
>
> == Repository Link ==
> You can review the full license text and documentation here:
> https://github.com/Luis-Harz/The-BOS-License
> Thank you very much for your time and for reviewing this submission. I
> look forward to hearing your feedback.
>
> Best regards,
> Luis Harz
>
> _______________________________________________
> 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
> License-review at lists.opensource.org
> http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org
More information about the License-review
mailing list