<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
While I appreciate the acknowledgement, my email comments on the
first version were not meant to describe every problem with this
license but simply were to demonstrate that there were significant
problems in the first few paragraphs, indicating that undoubtedly
the drafting problems were throughout. Making changes addressing
only my two original criticisms doesn't begin to solve all the
problems, and in fact the changes have made it much worse. Now I
don't even see a clear grant of a copyright license. This -- "Each
Contributor grants a royalty-free, perpetual, worldwide license
under their copyright ... they own or control that are necessarily
infringed by their Contributions, but only to the extent of the
changes they contributed" -- is nonsensical, if that's supposed to
be the grant.<br>
<br>
As Rob Landley points out, this is not a task for the layperson.<br>
<br>
Pam<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></div>
<br>
<div class="moz-cite-prefix">On 2/21/2026 5:28 AM, Timofey Zakharcuk
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOm0KL-+fyr6SRQ8123QB2u1By+P0W8Cn6RhAk_yKXGx8THTfA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Found a problem in my license, anti tivoization is
in the preamble, not the terms.
<div><br>
</div>
<div>Although the old LICENSE.txt doesn't work anymore, the
website is updated. although, here's the new file, still
called v1.0 to prevent "user confusion"</div>
<div><br>
</div>
<div>
<p><span style="white-space-collapse: preserve;">Best,</span></p>
<p><span style="white-space-collapse: preserve;">Timofey Zakharchuk</span></p>
</div>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Sat, Feb 21, 2026 at
3:53\u202fPM Timofey Zakharcuk <<a
href="mailto:timofey.zakharchuk.research@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">timofey.zakharchuk.research@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<p><span>I am submitting a revised version of the Open
Source Copyleft License (OSCL) v1.0, dated February 21,
2026, for consideration.</span></p>
<p><span><br>
</span></p>
<p><span>This license was not drafted by a lawyer. Instead,
it has been developed with respect for and in response
to the thoughtful feedback provided by OSI reviewers,
including Kevin P. Fleming and Pamela Chestek. Their
insights helped identify key areas for improvement, and
I am grateful for their time and expertise, honestly,
it'd fail on day 1 in not them!</span></p>
<p><span><br>
</span></p>
<p>Although the license is named v1.0, I want to note that
an earlier draft also used the v1.0 label. I\u2019ve kept the
revised version as v1.0 to avoid user confusion (e.g.,
\u2018why is there no v1.0?\u2019). The earlier version was never
adopted. </p>
<p><span><br>
</span></p>
<p><span>The License is hosted at:</span></p>
<p><a href="https://areponian.github.io/oscl.html"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://areponian.github.io/oscl.html</a><span> (
</span><a href="https://areponian.github.io/oscl.html"
target="_blank" moz-do-not-send="true">OSCL License \u2013
AREPONIAN Project</a> )</p>
<p>It's also in the submitted file LICENSE.txt</p>
<p><br>
</p>
<p>Off-topic note: some parts of the website (like the
buttons) don\u2019t currently work \u2014 it\u2019s in a very \u201cminimal\u201d
state right now \u2014 but the license text is fully hosted and
accessible .</p>
<p><br>
</p>
<p>Key improvements:</p>
<ul>
<li>
<p><span>Clearer definitions of Licensor, Contributor,
and Derivative Work</span></p>
</li>
<li>
<p><span>Expanded patent grants applying to Contributors
and Distributors</span></p>
</li>
<li>
<p><span>Explicit anti\u2011Tivoization protections</span></p>
</li>
<li>
<p><span>A stewardship clause for future license
versions</span></p>
</li>
<li>
<p><span>One\u2011way GPL compatibility (OSCL to GPL)</span></p>
</li>
<li>
<p><span><br>
</span></p>
</li>
<li>
<p>OSCL is philosophically close to the GPL: it
emphasizes user freedom and strong copyleft.<br>
It includes a preamble about free software and user
rights.<br>
At the same time, it resembles the MPL in its
compatibility model.<br>
OSCL allows one-way GPL compatibility (OSCL to GPL),
enabling integration without relicensing GPL code.<br>
</p>
</li>
<li>
<p><br>
</p>
</li>
<li>
<p>I welcome further review and discussion, and I am
committed to refining OSCL to meet OSI standards.<span></span></p>
</li>
<li>
<p><br>
</p>
</li>
<li>
<p>Best regards, Timofey Zakharchuk</p>
</li>
<li>
<p><a
href="mailto:timofey.zakharchuk.research@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">timofey.zakharchuk.research@gmail.com</a> </p>
</li>
</ul>
</div>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-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 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>