<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Dear Harz,<br>
<br>
Please provide the rest of the information that is required for a
license submission.<br>
<br>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
4641 Post St.<br>
Unit 4316<br>
El Dorado Hills, CA 95762<br>
+1 919-800-8033<br>
<a class="moz-txt-link-abbreviated" href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.chesteklegal.com">www.chesteklegal.com</a><br>
<br>
</div>
<div class="moz-cite-prefix">On 7/24/2026 3:33 AM, Harz Tronics
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALV9SKDEUq8rF5FAhjHj2eEa-P7niyddbLVJXBAR35--ACqRNw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Here is the revised BOS Public License v1.2, which
explicitly clarifies that attribution requirements apply solely
to source code releases and not to compiled binaries/object
code.
<div dir="auto"><br>
</div>
<div dir="auto">Here is the link: <a
href="https://github.com/Luis-Harz/The-BOS-License"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/Luis-Harz/The-BOS-License</a></div>
<div dir="auto"><br>
</div>
<div dir="auto">And here the full License:</div>
<div dir="auto">THE BOS PUBLIC LICENSE (Better Open Source)</div>
<div dir="auto">Version 1.2 Based on the MIT License with custom
attribution terms</div>
<div dir="auto">Copyright (c) 2026 [Your Name]</div>
<div dir="auto"><br>
</div>
<div dir="auto">Permission is hereby granted, free of charge, to
any person obtaining a copy</div>
<div dir="auto">of this software and associated documentation
files (the \u201cSoftware\u201d), to deal</div>
<div dir="auto">in the Software without restriction, including
without limitation the rights</div>
<div dir="auto">to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell</div>
<div dir="auto">copies of the Software, and to permit persons to
whom the Software is</div>
<div dir="auto">furnished to do so, subject to the following
conditions:</div>
<div dir="auto"><br>
</div>
<div dir="auto">The above copyright notice, this permission
notice, and the additional terms</div>
<div dir="auto">below shall be included in all copies, forks, or
substantial portions of the Software.</div>
<div dir="auto"><br>
</div>
<div dir="auto">ADDITIONAL TERMS:</div>
<div dir="auto">(Note: The additional terms below apply strictly
to public Source Code distribution and repositories, not to
compiled binaries or object code.)</div>
<div dir="auto"><br>
</div>
<div dir="auto">1. Original Project Link: Any public fork,
web-hosted repository, or public </div>
<div dir="auto"> republication of this Software (such as on
GitHub, GitLab, or similar platforms) </div>
<div dir="auto"> must contain a clearly visible and accessible
link back to its immediate </div>
<div dir="auto"> upstream repository in its primary
documentation (e.g., the README file or main </div>
<div dir="auto"> project description). This requirement
applies strictly to public code distribution </div>
<div dir="auto"> and repository forks; it does not apply to
private, internal, offline, or </div>
<div dir="auto"> execution-only use. In case the upstream
repository's URL becomes invalid, </div>
<div dir="auto"> deleted, private, or inaccessible, this
requirement is waived.</div>
<div dir="auto"><br>
</div>
<div dir="auto">2. Preservation of Credits: If the Software
contains a CREDITS.txt file, </div>
<div dir="auto"> existing names and credits within this file
must be preserved without removal </div>
<div dir="auto"> or alteration in all forks, modifications, or
republished versions of the </div>
<div dir="auto"> Software. You are permitted to add new
credits or names (for yourself or </div>
<div dir="auto"> other contributors) to the file.</div>
<div dir="auto"><br>
</div>
<div dir="auto">THE SOFTWARE IS PROVIDED \u201cAS IS\u201d, WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR</div>
<div dir="auto">IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY,</div>
<div dir="auto">FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE</div>
<div dir="auto">AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER</div>
<div dir="auto">LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM,</div>
<div dir="auto">OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
USE OR OTHER DEALINGS IN</div>
<div dir="auto">THE SOFTWARE.</div>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Fri, Jul 24, 2026, 12:20
Carlo Piana <<a href="mailto:carlo@piana.eu"
moz-do-not-send="true" class="moz-txt-link-freetext">carlo@piana.eu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div
style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000">
<div><br>
</div>
<div><br>
</div>
<hr id="m_-6590942321337918199zwchr">
<div>
<blockquote
style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>Da:
</b>"Harz Tronics" <<a
href="mailto:harztronicsgmbh@gmail.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">harztronicsgmbh@gmail.com</a>><br>
<b>A: </b>"Carlo Piana" <<a
href="mailto:carlo@piana.eu" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">carlo@piana.eu</a>><br>
<b>Inviato: </b>Venerdì, 24 luglio 2026 10:30:27<br>
<b>Oggetto: </b>Re: [License-review] For Approval:
The BOS Public License v1.0<br>
</blockquote>
</div>
<div>
<blockquote
style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="auto">Hello Carlo,
<div dir="auto"><br>
</div>
<div dir="auto">Thank you for your feedback and
perspective from the compliance side. I would like
to clarify a few points and share the updated
context with Version 1.1:</div>
</div>
</blockquote>
<div><br>
</div>
<div>Please retract the previous versione and apply for
the new one. Also, you seem to have replied to me
only, this discussion should be public. Can you bring
it back to the list?</div>
<div><br>
</div>
<div>Also, see the requirements for the submission
(Pam's email).</div>
<div><br>
</div>
<blockquote
style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">1. Downstream Rights & Credits:
In V1.1, I explicitly clarified that downstream
authors and contributors are fully encouraged to
add their own names/credits to CREDITS.txt. The
requirement only ensures that existing upstream
credits are not stripped away.</div>
</div>
</blockquote>
<div><br>
</div>
OK, this is similar to what happens in other contexts,
so I think it's legit. That was not transparent since we
could not see the text. But does this apply only to
source or also to object code? Because in the second
case it would be shifting to some copyleft.
<div><br>
</div>
<blockquote
style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="auto">
<div dir="auto">2. Invalid/Offline Links: V1.1
includes an explicit waiver clause. If an upstream
repository becomes private, deleted, or
unavailable, the backlink requirement is
completely waived to prevent legal traps for
downstream users.</div>
</div>
</blockquote>
<div><br>
</div>
<div>OK, this fixes at least one of my untold concerns.</div>
<blockquote
style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">3. Friction & Rationale: The
motivation comes from the modern "single-click
republication" ecosystem on platforms like GitHub
or GitLab. The requirement is meant to be minimal:
standard platform forks (which display origin
links by default) or a simple line in the README
already fully satisfy this condition.</div>
</div>
</blockquote>
My objection still stands. And IMHO it creates bigger
problems than the fixed ones.
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Carlo</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
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
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</body>
</html>