<div dir="auto"><div>Once the submitter stated that he did not intend to use an attorney for drafting, preferring community review, I turned out. </div><div dir="auto"><br></div><div><br></div><div data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div>Bruce Perens K6BP</div></div></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Jan 24, 2026, 15:23 Pamela Chestek <<a href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<p>This license is a good example of why it is highly unlikely that
a license not written by a lawyer can be approved. Legal writing
is very formulaic with a number of interpretive principles applied
when they are written. If you are not familiar with these
principles and following standard drafting practices, there is a
high risk that the legal document will not function as intended. I
did not read much past the definitions section and spotted many,
many drafting problems. </p>
<p>I am looking at the version of the license you submitted to
license-discuss on January 21 at 10:10 am PST; there are so many
versions I'm not sure what's what. I see that the one you just
submitted to license-review appears substantially different but I
haven't looked at that license.<br>
<br>
In terms of drafting problems, first, a preamble is to provide
context for interpretation of the operative terms of the
agreement. When an agreement is well-drafted, the preamble does
not have any operative terms in it. The reason is when you say the
same thing twice, once in the preamble and then in the terms, you
have almost surely created a loophole or ambiguity. The preamble
is also not a place to explain what you're trying to do - what
you're trying to do should be clear from the terms of the
agreement. If you have to explain what you are trying to do in the
preamble, then there may be something wrong with how you've
written the terms. <br>
<br>
With that context, your preamble is problematic. As an easy
example, you grant a patent license in the preamble, stating "Each
contributor to a covered Work grants a non-exclusive, worldwide,
royalty-free patent license ..." and also grant a license in
section VIII. Undoubtedly these two grants can be interpreted in
different ways because anytime you say things twice, unless they
are <i>exactly</i> the same, you created the potential for two
different interpretations. As another example, you say in the
preamble "this License does not impose any obligation to
distribute future versions of a Work under the same terms."
However, in Section III(c) you say "You must license the modified
Work, as a whole, under this License ..." Isn't a "future version"
also a "modified Work"? So which is correct?<br>
<br>
You have even blurred the line between operative terms and the
preamble in your own questions. Below you say</p>
<p>
<blockquote type="cite">
<div>1. Explicit opt-in for network-based source obligations</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> This License does not require network-based source
disclosure </div>
<div>> unless the copyright holder has expressly chosen to
enable such </div>
<div>> obligations by an Explicit Network Use Notice.</div>
<div><br>
</div>
<div>> \u201cExplicit Network Use Notice\u201d means a clear and
prominent notice </div>
<div>> placed by the copyright holder stating that operation
of the Work </div>
<div>> through a computer network shall be treated as
conveying for the </div>
<div>> purposes of source availability.</div>
</blockquote>
<br>
The text you quote, "This License does not require ...", is in the
preamble. It is immediately followed by the sentence "The binding
terms governing use, modification, and conveyance of covered Works
are set forth below." So you have quoted a part of the agreement
that isn't a operative term for your statement that there isn't a
requirement to disclose source code unless one opts in.</p>
<p>When I dig deeper and try to figure how this requirement is
manifested in the actual terms of the agreement, it's anything but
clear. There is something called an "Explicit Network Use Notice"
where,"If the Work, or a modified version of the Work, is operated
primarily for the purpose of providing its functionality or output
to third parties through a computer network, including via hosted,
remote, or internet-accessible services, such operation may be
treated as conveyance solely for the purpose of triggering the
source availability obligations expressly set forth in this
License, where an Explicit Network Use Notice applies." There is
nothing in the license that says where this notice is supposed to
be - is it appended to the license, is it in the documentation, is
it on a webpage somewhere, how is the user supposed to know
whether or not they've located the "Explicit Network Use Notice"?
If this is acceptable for an open source license at all (and I
agree with Bruce that this mechanism, in effect, means this is two
different licenses, one that treats availability remotely as a
"conveyance" and one that does not), it is poorly implemented.</p>
<p>Moving to the definitions, I stopped after the first two.</p>
<p>
<blockquote type="cite">
<div>"Compatible License" means a license that is compatible
with this</div>
<div>License under applicable copyright law, without imposing
additional</div>
<div>restrictions on the exercise of the rights granted under
this License.</div>
</blockquote>
Defining "compatible" circularly as "compatible" isn't helpful. In
my experience, license compatibility is a concept unique to open
source licenses, and I bet if you polled open source lawyers even
they wouldn't agree on exactly what it means. So this term
probably needs more explanation.
<blockquote type="cite">
<div><br>
</div>
<div> "Copyright" refers to laws similar to copyright that apply
to other</div>
<div>types of Works, such as semiconductor chips.</div>
<div><br>
</div>
</blockquote>
What, the term "Copyright" doesn't include copyright law itself,
only laws "similar" to copyright law?? </p>
<p>I didn't review all the definitions, but I assume there others
have similar flaws.</p>
<p>And, although you have a definitions section, there are also
multiple definitions in at least Sections II and VIII for terms
that are used throughout the agreement. It's okay to have a
definition within a section if it's only relevant to that section
(like "entity transaction" in Section VII), but if someone needs
to go find a definition it should be easy to find. </p>
<p>There are numbered and unnumbered subsections. The unnumbered
parts appear to be explanatory material, so I question whether
they belong in the agreement at all. If they are needed, they
should be numbered so they can be easily referenced, either
elsewhere in the document or when talking about the document, as
we are doing here.</p>
<p>The OSI does not approve licenses that are poorly drafted, so
these are problems that have to be fixed before you submit the
license for approval. These, and many other issues, are all
problems that a lawyer skilled in drafting would avoid. </p>
<p>You also asked some policy questions:</p>
<p>
<blockquote type="cite">
<div>- Explicit opt-in treatment of network-based source
obligations </div>
</blockquote>
This makes use and adoption of the license more challenging for
several reasons. First is practical; you haven't made it easy for
a user to figure out whether they have the obligation or not.
Second is that adoption is more unlikely because the compliance
obligations are more complicated. Or should the user just assume
that all the works under this license have the notice and meet the
more stringent compliance obligations, to make their lives
simpler? In that case you've undermined your reason for relieving
them of the obligation. License compliance is already quite
difficult and you're making it harder. The OSI only approves
licenses that have a potential audience larger than just one
project, and this complexity is a strike against it.</p>
<p>I also don't see the niche that this option fills. In the network
context, if someone doesn't want to impose any compliance
obligations for a network service, then use the GPL. If you want
to impose them, then use the AGPL. So what unserved need does this
license fill?
<blockquote type="cite">
<div>- Network operation triggers source availability only, not
full conveyance </div>
</blockquote>
I don't know what you mean by "full conveyance." To "convey" is
defined as "any kind of propagation that enables other parties to
make or receive copies ...", so I don't know what "full" means in
association with the word "conveyance." </p>
<p>I assume what you are trying to say is that someone providing the
software as a service over a network has a more limited set of
obligations than someone who is distributing the software. If
that's the meaning, there are clearer ways to state it in the
text. Your quoted language uses "source availability obligations"
without either defining it or pointing to a section number, which
creates significant interpretation problems. But I don't see a
problem with the concept under open source principles that some
users have fewer obligations than others, as long as the rights of
the least privileged are sufficient.
<blockquote type="cite">
<div>- Service-aware definition of Corresponding Resource</div>
</blockquote>
I don't see the definition of "Corresponding Resource" as narrower
than Source Code or service-aware. The definition of
"Corresponding Resource"<i> </i>starts with "all Source Code
required to generate, install, run, and modify the Work, including
...." and then adds more components. The definition of "Source
Code" also has its own laundry list of parts, "includ[ing] all
files, definitions, scripts, build instructions, and materials
necessary ..." So if you are saying that someone providing the
software over a network only has to provide "Corresponding
Resource," the definitions say they have to provide the Source
Code plus something more - or maybe not, depending on the
congruence of the laundry lists for the two definitions. You also
use the term "Corresponding Resource" in the definition of "User
Product," which is not a network interaction, further confusing
things. So I don't think you've accomplished what you were trying
to accomplish.</p>
<p>
<blockquote type="cite">
<div>- Anti-gatekeeping and equal-access requirements </div>
</blockquote>
I believe you go too far when you say a distributor must not
condition access on "payment, exclusive agreements, subscription
status, [or] customer classification." What this means is that the
"Corresponding Resource" must be made available to the public.
This is beyond what the GPL requires, which is that you only have
to give the source code to those who have the object code, not the
public at large. You are also possibly saying that the code has to
be maintained in perpetuity because someone's "policy" of deleting
deprecated versions interferes with access. I think the concept is
fine, but the way its been implemented is overreaching.
<blockquote type="cite">
<div>- Managed platforms and technological measures</div>
<div><br>
</div>
</blockquote>
The license says</p>
<p>
<blockquote type="cite">
<div>This Section does not prohibit the use of technical
mechanisms that are</div>
<div>designed solely to ensure system integrity, security,
authenticity, or</div>
<div>reliable distribution, including but not limited to secure
boot</div>
<div>mechanisms, cryptographic signature verification, or
platform-level</div>
<div>distribution requirements, provided that such mechanisms do
not prevent</div>
<div>recipients from accessing, modifying, or conveying the
Corresponding</div>
<div>Resource of the covered Work under the terms of this
License.</div>
</blockquote>
<br>
I believe this is an acceptable provision and may not even go far
enough. Right now the Software Freedom Conservancy is trying to
assert a right to reinstall the software on the original device.
Your requirement doesn't assure that, but perhaps it should, with
"accessing, modifying, conveying <i>and reinstalling</i> ...."</p>
<p>To summarize, the OSI can't overlook poor quality drafting; the
quality of the writing is as important as the rights and
obligations you are trying to convey because the rights and
obligations can't be observed as you intend if they aren't stated
in a clear and precise way with as little ambiguity as humanly
possible. You have told us what you are trying to do with the
license, but the question is whether the language of the license
actually does what you are trying to do, and at the moment it does
not.</p>
<p>Finally, my comments are by no means comprehensive and are just
exemplary, to demonstrate the kinds of problems that the document
contains. I am sympathetic to what you want to do, but this
license is never going to be a high enough quality for the OSI to
approve if you don't have it cleaned up by a contract lawyer who
is at least familiar with, if not highly skilled in, open source
licenses. </p>
<p>Pam</p>
<div>Pamela S. Chestek<br>
Chestek Legal<br>
<a href="https://www.google.com/maps/search/4641+Post+St.+%0D%0A++++++Unit+4316+%0D%0A++++++El+Dorado+Hills,+CA+95762?entry=gmail&source=g">4641 Post St.</a><br><a href="https://www.google.com/maps/search/4641+Post+St.+%0D%0A++++++Unit+4316+%0D%0A++++++El+Dorado+Hills,+CA+95762?entry=gmail&source=g">
Unit 4316</a><br><a href="https://www.google.com/maps/search/4641+Post+St.+%0D%0A++++++Unit+4316+%0D%0A++++++El+Dorado+Hills,+CA+95762?entry=gmail&source=g">
El Dorado Hills, CA 95762</a><br>
+1 919-800-8033<br>
pamela@chesteklegal<br>
<a href="http://www.chesteklegal.com" target="_blank" rel="noreferrer">www.chesteklegal.com</a><br>
<br>
<br>
</div>
<div>On 1/22/2026 6:07 AM, M.samet Duman via
License-discuss wrote:<br>
</div>
<blockquote type="cite">
<div>Hello Bruce, </div>
<div>Hello all,</div>
<div><br>
</div>
<div>Thank you for the guidance. I understand the concern about
review scope and time investment.</div>
<div><br>
</div>
<div>Based strictly on the current PT-GPL v2 text, below are five
specific areas where the license is intended to diverge from
existing copyleft licenses. For each point, I have included only
the relevant operative language, followed by a short statement
of intent.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>1. Explicit opt-in for network-based source obligations</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> This License does not require network-based source
disclosure </div>
<div>> unless the copyright holder has expressly chosen to
enable such </div>
<div>> obligations by an Explicit Network Use Notice.</div>
<div><br>
</div>
<div>> \u201cExplicit Network Use Notice\u201d means a clear and
prominent notice </div>
<div>> placed by the copyright holder stating that operation of
the Work </div>
<div>> through a computer network shall be treated as conveying
for the </div>
<div>> purposes of source availability.</div>
<div><br>
</div>
<div>Intent: </div>
<div>Unlike AGPL-style copyleft, network-based obligations are not
automatic. The copyright holder explicitly decides whether
network operation should trigger source availability.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>2. Network operation triggers source availability only, not
full conveyance</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> Such operation may be treated as conveyance solely for
the purpose </div>
<div>> of triggering the source availability obligations
expressly set forth </div>
<div>> in this License, where an Explicit Network Use Notice
applies.</div>
<div><br>
</div>
<div>> This License does not require disclosure of unrelated
systems, </div>
<div>> independent services, or proprietary infrastructure that
are not </div>
<div>> derived from the covered Work itself.</div>
<div><br>
</div>
<div>Intent: </div>
<div>This deliberately limits the legal effect of network use,
avoiding spillover into unrelated systems or services.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>3. Service-aware definition of Corresponding Resource</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> Corresponding Resource means all Source Code required to
generate, </div>
<div>> install, run, and modify the Work, including build
scripts, interface </div>
<div>> definitions, and supporting code specifically designed
for or tightly </div>
<div>> coupled to the Work.</div>
<div><br>
</div>
<div>> Corresponding Resource includes only those configuration
or integration </div>
<div>> components that are specifically written to make the
covered Work </div>
<div>> function as a network-accessible service, and does not
include general </div>
<div>> infrastructure or unrelated systems.</div>
<div><br>
</div>
<div>Intent: </div>
<div>This explicitly includes service glue and deployment-specific
code, while drawing a clear boundary around general
infrastructure.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>4. Anti-gatekeeping and equal-access requirements</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> Any technical, contractual, procedural, or policy-based
measure that </div>
<div>> has the effect of discouraging, delaying, conditioning,
or preventing </div>
<div>> access to the Corresponding Resource constitutes a
failure to comply </div>
<div>> with the requirements of this License.</div>
<div><br>
</div>
<div>> Availability shall not be conditioned on exclusive
agreements, </div>
<div>> non-disclosure obligations, account registration,
payment, or </div>
<div>> acceptance of terms inconsistent with this License.</div>
<div><br>
</div>
<div>Intent: </div>
<div>This addresses modern access barriers common in hosted and
SaaS-style distribution models that are not explicitly handled
in GPL.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>5. Managed platforms and technological measures</div>
<div><br>
</div>
<div>Relevant text:</div>
<div>> The obligations created by this License arise
exclusively from its </div>
<div>> operative provisions and are independent of such
external constraints.</div>
<div><br>
</div>
<div>> Technical mechanisms \u2026 are permitted provided that such
mechanisms </div>
<div>> do not prevent recipients from accessing, modifying, or
conveying </div>
<div>> the Corresponding Resource of the covered Work under the
terms of </div>
<div>> this License.</div>
<div><br>
</div>
<div>Intent: </div>
<div>This generalizes anti-tivoization principles to managed and
platform-controlled environments, without prohibiting legitimate
security mechanisms.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>If this format is useful, I can extract additional points in
the same way for further discussion.</div>
<div><br>
</div>
<div>Thank you for taking the time to review this.</div>
<div><br>
</div>
<div>Best regards, </div>
<div>Mehmet Samet Duman </div>
<div>Author of Project Tick</div>
<div><br>
<blockquote type="cite">
<div>Bruce Perens <a href="mailto:bruce@perens.com" target="_blank" rel="noreferrer"><bruce@perens.com></a> \u015funlar\u0131 yazd\u0131 (22
Oca 2026 06:14):</div>
<br>
<div>
<div dir="ltr"><br>
<div>I would like you to extract the relevant text for
each of the 5 points you'd like feedback upon, and
present the relevant and innovative text, only, with
each point. I think this would be a manageable chunk
that people could look at and comment upon without
taking a large part of their day. I don't represent
anyone but me, but given the dearth of other
participation so far, I am assuming that other folks
would like that too.</div>
<div><br>
</div>
<div> Thanks</div>
<div><br>
</div>
<div> Bruce</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jan 21, 2026 at
3:56\u202fPM M.samet Duman <<a href="mailto:dumanmehmetsamet@icloud.com" target="_blank" rel="noreferrer">dumanmehmetsamet@icloud.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>
<div>Hello Bruce, </div>
<div>Hello all,</div>
<div><br>
</div>
<div>Thank you for the feedback. Based on it, I am
sharing a revised draft of the Project Tick General
Public License v2.</div>
<div><br>
</div>
<div>To avoid unnecessary review burden, I want to be
explicit about what feedback I am asking for and
what I am not:</div>
<div><br>
</div>
<div>
<div>- I am aware of the concern regarding GPL text
derivation; this draft does not</div>
<div> assert originality of expression and is
presented solely to discuss</div>
<div> behavioral differences, not to request
approval of a new GPL variant.</div>
</div>
<div>- I am not asking for a line-by-line legal review
of the entire text.</div>
<div>- I am not claiming originality of wording
relative to GPL text.</div>
<div>- I am asking whether the specific behavioral
mechanisms described below are</div>
<div> useful, redundant, or problematic from an Open
Source Definition perspective.</div>
<div><br>
</div>
<div>In particular, feedback is requested only on
these points:</div>
<div><br>
</div>
<div>- Explicit opt-in treatment of network-based
source obligations </div>
<div>- Separation of operation from conveyance as
legal concepts </div>
<div>- Narrow, explicit definition of Corresponding
Resource for service deployment </div>
<div>- Clear fencing of all explanatory material as
non-normative </div>
<div>- Absence of any ecosystem-level interpretive or
compatibility authority</div>
<div><br>
</div>
<div>The full draft is included below the signature
for reference only, since the license has not yet
been published elsewhere. No approval is requested
at this stage.</div>
<div><br>
</div>
<div>If it would be preferable, I am happy to extract
and discuss only individual clauses in follow-up.</div>
<div><br>
</div>
<div>Thank you again for the candid feedback and time.</div>
<div><br>
</div>
<div>Best regards, </div>
<div>Mehmet Samet Duman </div>
<div>Author of Project Tick</div>
<div><br>
</div>
<div>\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013\u2013</div>
<div>Below is the current draft of the Project Tick
General Public License,</div>
<div>Version 2. This text is provided for reference
and discussion only and is not yet</div>
<div>finalized or published.</div>
<div><br>
</div>
<div>
<div>PROJECT TICK GENERAL PUBLIC LICENSE</div>
<div>Version 2, 2 February 2026</div>
<div><br>
</div>
<div>Copyright (C) 2026 Project Tick <<a href="https://projecttick.org/" target="_blank" rel="noreferrer">https://projecttick.org/</a>></div>
<div>Everyone is permitted to copy and distribute
verbatim copies</div>
<div>of this license document, but changing it is
not allowed.</div>
<div>This is the canonical text of the Project Tick
General Public</div>
<div>License, Version 2. Works licensed under this
text are governed</div>
<div>exclusively by Version 2 of the License, unless
the applicable</div>
<div>copyright holder explicitly authorizes the use
of another version.</div>
<div><br>
</div>
<div>Preamble</div>
<div><br>
</div>
<div>The Project Tick General Public License is a
copyright-based copyleft</div>
<div>license intended for software programs, as
designated by the applicable</div>
<div>copyright holder. Unless expressly stated
otherwise, this License</div>
<div>applies to the Work solely in its capacity as
software.</div>
<div><br>
</div>
<div>This License is designed to ensure that
recipients of a covered Work</div>
<div>can effectively access, study, modify, and
share that Work, without</div>
<div>being subjected to restrictions that undermine
the practical exercise</div>
<div>of those rights.</div>
<div><br>
</div>
<div>By applying this License, a copyright holder
authorizes recipients to</div>
<div>use, modify, and convey the Work under a
consistent set of conditions.</div>
<div>Any party that conveys a covered Work must do
so in a manner that</div>
<div>preserves the same rights and obligations for
all downstream recipients.</div>
<div><br>
</div>
<div>This License places particular emphasis on the
availability of the</div>
<div>Work in forms suitable for modification and
reuse. Where a covered Work</div>
<div>is conveyed together with its preferred form
for modification, access</div>
<div>to that form must be provided in a manner
consistent with this License.</div>
<div>A copy of this License must accompany all
conveyances of the Work.</div>
<div><br>
</div>
<div>The License also defines the scope of permitted
use, modification, and</div>
<div>conveyance in a clear and predictable manner,
while disclaiming</div>
<div>warranties for the Work. Unless the copyright
holder explicitly states</div>
<div>otherwise, this License does not impose any
obligation to distribute</div>
<div>future versions of a Work under the same terms.</div>
<div><br>
</div>
<div>Some devices or deployment environments may
impose technical or design</div>
<div>constraints that affect the execution of
modified versions of a Work.</div>
<div>The obligations created by this License arise
exclusively from its</div>
<div>operative provisions and are independent of
such external constraints.</div>
<div><br>
</div>
<div>Each contributor to a covered Work grants a
non-exclusive, worldwide,</div>
<div>royalty-free patent license limited to what is
necessary to exercise</div>
<div>the rights granted under this License with
respect to that contributor\u2019s</div>
<div>contributions.</div>
<div><br>
</div>
<div>This License preserves the core freedoms and
obligations commonly</div>
<div>associated with established copyleft licenses,
while explicitly</div>
<div>extending those principles to network-based
operation, managed</div>
<div>deployment environments, and service-oriented
use cases that are</div>
<div>not consistently addressed by traditional
distribution-focused models.</div>
<div><br>
</div>
<div>In practical terms, this License is intended to
be understandable</div>
<div>and usable by individual developers, small
teams, and community</div>
<div>projects, not only by legal experts. It does
not require permission</div>
<div>to use or study the Work, and it does not
restrict private,</div>
<div>experimental, or non-public use. Its
obligations apply only when</div>
<div>the Work is shared with others or used to
provide its functionality</div>
<div>to the public.</div>
<div><br>
</div>
<div>This License does not require network-based
source disclosure</div>
<div>unless the copyright holder has expressly
chosen to enable such</div>
<div>obligations by an Explicit Network Use Notice.</div>
<div><br>
</div>
<div>The binding terms governing use, modification,
and conveyance of</div>
<div>covered Works are set forth below.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>------------------------ TERMS AND CONDITIONS
-----------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>------------------ PART I \u2014 CORE RIGHTS AND
OBLIGATIONS -------------------</div>
<div>The provisions of this Part define the
essential permissions, conditions, -</div>
<div>and obligations of this License. Compliance
with this Part is mandatory for</div>
<div>any use, modification, operation, or conveyance
of a covered Work. --------</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>I. Definitions.</div>
<div><br>
</div>
<div>"This License" refers to the Project Tick
General Public License,</div>
<div>Version 2.</div>
<div><br>
</div>
<div>"Compatible License" means a license that is
compatible with this</div>
<div>License under applicable copyright law, without
imposing additional</div>
<div>restrictions on the exercise of the rights
granted under this License.</div>
<div><br>
</div>
<div>"Copyright" refers to laws similar to copyright
that apply to other</div>
<div>types of Works, such as semiconductor chips.</div>
<div><br>
</div>
<div>"Work" means a software program licensed under
this License.</div>
<div>Each licensee is referred to as "you".
"Recipients" may be</div>
<div>individuals or organizations.</div>
<div><br>
</div>
<div>To "modify" a Work means to copy from or adapt
all or part of the</div>
<div>Work in a fashion requiring copyright
permission, other than the</div>
<div>making of an exact copy. The resulting Work is
called a "modified</div>
<div>version" of the earlier Work or a Work "based
on" the earlier Work.</div>
<div><br>
</div>
<div>To "convey" a Work means any kind of
propagation that enables other</div>
<div>parties to make or receive copies of the Work.
Mere interaction with</div>
<div>a user through a computer network, without the
transfer of a copy,</div>
<div>does not by itself constitute conveying.</div>
<div><br>
</div>
<div>"Explicit Network Use Notice" means a clear and
prominent notice</div>
<div>placed by the copyright holder stating that
operation of the Work</div>
<div>through a computer network shall be treated as
conveying for the</div>
<div>purposes of source availability.</div>
<div><br>
</div>
<div>To "operate" a Work means to run, deploy, or
make functional use</div>
<div>of the Work for the primary purpose of
providing its functionality</div>
<div>or output to third parties as a service or
system, whether directly</div>
<div>or indirectly, including through a computer
network, where such parties</div>
<div>are not under the direct control of the
operator.</div>
<div><br>
</div>
<div>A "Library Work" is a Work that is designed to
provide reusable</div>
<div>functionality intended to be linked, imported,
or otherwise combined</div>
<div>with other independent Works, without, by its
nature, forming a single</div>
<div>Combined Work merely by being present.</div>
<div><br>
</div>
<div>"User Product" means (1) any tangible personal
property which is</div>
<div>normally used for personal, family, or domestic
purposes, and (2)</div>
<div>anything designed or sold for incorporation
into a dwelling. In</div>
<div>determining whether a product is a User
Product, doubtful cases shall</div>
<div>be resolved in favor of coverage. For a
particular product received</div>
<div>by a particular user, "normally used" refers to
the typical or common</div>
<div>use of that class of product, regardless of the
status of the particular</div>
<div>user or the way in which the particular user
actually uses, expects</div>
<div>to use, or is expected to use the product.</div>
<div><br>
</div>
<div>"Installation Information" for a User Product
means any methods,</div>
<div>procedures, authorization keys, or other
information required to</div>
<div>install and run modified versions of a covered
Work in that User</div>
<div>Product from a modified version of its
Corresponding Resource. The</div>
<div>information must be sufficient to ensure that
the continued operation</div>
<div>of the modified object code is not prevented or
interfered with solely</div>
<div>because the Work has been modified.</div>
<div><br>
</div>
<div>A "Combined Work" is a Work produced by
linking, importing, or</div>
<div>otherwise combining a Library Work with another
independent Work,</div>
<div>whether statically or dynamically.</div>
<div><br>
</div>
<div>An interactive user interface displays
"Appropriate Legal Notices"</div>
<div>to the extent that it includes a convenient and
prominently visible</div>
<div>feature that (1) displays an appropriate
copyright notice, and (2)</div>
<div>tells the user that there is no warranty for
the Work (except to the</div>
<div>extent that warranties are provided), that
licensees may convey the</div>
<div>Work under this License, and how to view a copy
of this License. If</div>
<div>the interface presents a list of user commands
or options, such as a</div>
<div>menu, a prominent item in the list meets this
criterion.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>II. Source Code and Corresponding Resource.</div>
<div><br>
</div>
<div>"Source Code" means the preferred form of the
Work for making</div>
<div>modifications to it. It includes all files,
definitions, scripts,</div>
<div>build instructions, and materials necessary to
understand, modify,</div>
<div>build, install, and run the Work in practice,
in a form that is</div>
<div>reasonably suitable for editing. "Object Code"
means any form of</div>
<div>the Work that is not Source Code. Deliberate
obfuscation, minification,</div>
<div>code generation output without the
corresponding human-readable input,</div>
<div>or any other transformation that materially
impairs the readability,</div>
<div>auditability, or modifiability of the Work
shall not be considered</div>
<div>Source Code. "Standard Interface" refers to
either a formal standard</div>
<div>defined by a recognized standards organization,
or, where applicable,</div>
<div>an interface that is widely used and publicly
documented among</div>
<div>practitioners working in the relevant language,
platform, or</div>
<div>ecosystem. The "System Libraries" of an
executable Work include</div>
<div>components that (1) are included as part of the
normal packaging</div>
<div>of a Main Component, but are not part of the
Work itself, and (2)</div>
<div>serve only to enable use of the Work with that
Main Component or</div>
<div>with an implementation of a Standard Interface.
In this context,</div>
<div>a "Main Component" refers to a kernel,
operating system, window</div>
<div>system, compiler, runtime, or object code
interpreter used to run</div>
<div>the Work. For a Work conveyed in object code or
other non-source form,</div>
<div>"Corresponding Resource" means all Source Code
required to generate,</div>
<div>install, run, and modify the Work, including
build scripts, interface</div>
<div>definitions, and supporting code specifically
designed for or tightly</div>
<div>coupled to the Work. The Corresponding Resource
does not include System</div>
<div>Libraries, general-purpose development tools,
or third-party components</div>
<div>that are not derived from the Work and are not
required for its modification</div>
<div>or the exercise of rights granted under this
License. Any portion of the Work</div>
<div>that is licensed under this License must remain
licensed under this License.</div>
<div>This License does not require relicensing of
independent third-party components.</div>
<div>For a Work conveyed in Source Code form, the
Source Code itself constitutes the</div>
<div>Corresponding Resource.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>III. Transmission of Modified Source Versions.</div>
<div><br>
</div>
<div>You may convey a Work based on the Work, or
modifications derived from</div>
<div>the Work, in Source Code form under the terms
of Section 5, provided</div>
<div>that you also comply with all of the following
conditions:</div>
<div><br>
</div>
<div> a) The modified Work must contain prominent
notices stating that you</div>
<div> have modified it, together with the date
of each such modification.</div>
<div><br>
</div>
<div> b) The modified Work must contain clear
notices stating that it is</div>
<div> licensed under this License, together with
any applicable additional</div>
<div> permissions expressly permitted under this
License. Such notices may</div>
<div> replace or update existing notices to
accurately reflect the modified</div>
<div> status of the Work.</div>
<div><br>
</div>
<div> c) You must license the modified Work, as a
whole, under this License</div>
<div> to any recipient who receives a copy of
it. This License, and any</div>
<div> applicable additional permissions
permitted by it, shall therefore</div>
<div> apply to the modified Work and all of its
parts, regardless of how they</div>
<div> are packaged or distributed.</div>
<div><br>
</div>
<div>This License does not permit relicensing of the
modified Work under</div>
<div>different terms. However, this provision does
not invalidate permissions</div>
<div>that you may have obtained separately and
independently from the</div>
<div>copyright holders of portions of the Work.</div>
<div><br>
</div>
<div> d) If the modified Work includes interactive
user interfaces, such</div>
<div> interfaces must display Appropriate Legal
Notices, unless the original</div>
<div> Work did not include such notices and the
nature of the interface makes</div>
<div> their display impractical or unreasonable.</div>
<div><br>
</div>
<div> e) If the modified Work is a Library Work,
the Library Work itself must</div>
<div> remain licensed under this License.
Linking, importing, or otherwise</div>
<div> using a Library Work in combination with
other independent Works does</div>
<div> not remove or alter the obligations
imposed by this License on the</div>
<div> Library Work itself, nor does it grant
permission to relicense the</div>
<div> Library Work under different terms.</div>
<div><br>
</div>
<div>A compilation of a covered Work with other
separate and independent</div>
<div>Works that are not, by their nature, extensions
of the covered Work and</div>
<div>that are not combined with it to form a single
unified Work is referred</div>
<div>to as an "aggregate". The inclusion of a
covered Work in an aggregate</div>
<div>does not cause this License to apply to the
other Works in the aggregate,</div>
<div>provided that the compilation and its
conveyance do not impose</div>
<div>additional restrictions on the rights granted
under this License with</div>
<div>respect to the covered Work.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>IV. Transmission of Non-Source Formats.</div>
<div><br>
</div>
<div>For the purposes of this Section, "Network
Interaction" means operation</div>
<div>of a Work through a computer network primarily
for the purpose of</div>
<div>providing its functionality or output to third
parties, regardless of</div>
<div>whether a copy of the Work is transferred.</div>
<div><br>
</div>
<div>This provision is not intended to discourage
legitimate service</div>
<div>deployment, experimentation, or
community-hosted use of covered</div>
<div>Works. Its purpose is solely to ensure that
recipients interacting</div>
<div>with a covered Work through a network are
afforded the same practical</div>
<div>freedoms to access, study, and modify the Work
as recipients who</div>
<div>receive copies through traditional
distribution.</div>
<div><br>
</div>
<div>In particular, this License does not require
disclosure of unrelated</div>
<div>systems, independent services, or proprietary
infrastructure that</div>
<div>are not derived from the covered Work itself.</div>
<div><br>
</div>
<div>Operating a covered Work through Network
Interaction primarily for the</div>
<div>purpose of providing its functionality or
output to the public may be</div>
<div>treated as conveying the Work where the
copyright holder has expressly</div>
<div>required such treatment by an explicit notice
solely for the purposes</div>
<div>of triggering the source availability
obligations set forth in this</div>
<div>License. This does not include internal,
private, testing, development,</div>
<div>or incidental uses that do not primarily
provide the Work\u2019s functionality</div>
<div>to the public. In accordance with Sections 4
and 5, you may convey a</div>
<div>covered Work in object code or other non-source
form, provided that the</div>
<div>Corresponding Resource of the Work is made
available under the terms of</div>
<div>this License in a machine-readable form. The
Corresponding Resource must</div>
<div>be made available in a manner that is no less
accessible, timely, and usable</div>
<div>than the object code itself.</div>
<div><br>
</div>
<div> a) You may convey the object code in, or
embodied in, a physical</div>
<div> product (including a physical distribution
medium), accompanied by</div>
<div> the Corresponding Resource fixed on a
durable physical medium</div>
<div> customarily used for software exchange.</div>
<div><br>
</div>
<div> b) You may convey the object code in, or
embodied in, a physical</div>
<div> product (including a physical distribution
medium), accompanied by a</div>
<div> written offer, valid for at least three
years and for as long as you</div>
<div> offer spare parts, updates, or customer
support for that product</div>
<div> model, to provide any recipient with
either:</div>
<div><br>
</div>
<div> (1) a copy of the Corresponding Resource
for all covered Works in</div>
<div> the product, on a durable physical
medium customarily used for</div>
<div> software exchange, for a price no
higher than the reasonable</div>
<div> cost of physically performing this
transmission; or</div>
<div><br>
</div>
<div> (2) immediate and unrestricted access to
copy the Corresponding</div>
<div> Resource through any reasonable and
publicly accessible means.</div>
<div><br>
</div>
<div>The refusal or non-acceptance of such a written
offer by any recipient</div>
<div>does not relieve you of the obligation to
ensure that the</div>
<div>Corresponding Resource remains publicly
available under this License</div>
<div>for the duration required by this Section.</div>
<div><br>
</div>
<div> c) You may convey individual copies of the
object code together with a</div>
<div> copy of the written offer described in
subsection (b), but only</div>
<div> occasionally, for non-commercial purposes,
and only if you received</div>
<div> the object code accompanied by such an
offer.</div>
<div><br>
</div>
<div> d) You may convey the object code by offering
access from a designated</div>
<div> location, free of charge or for a fee,
provided that equivalent access</div>
<div> to the Corresponding Resource is offered
in the same manner, without</div>
<div> delay, additional conditions, or practical
barriers. If the object</div>
<div> code is offered from a network server, the
Corresponding Resource may</div>
<div> be hosted on a different server operated
by you or by a third party,</div>
<div> provided that clear, prominent, and
persistent instructions are given</div>
<div> alongside the object code indicating where
and how the Corresponding</div>
<div> Resource may be obtained.</div>
<div><br>
</div>
<div>Any technical, contractual, procedural, or
policy-based measure that</div>
<div>has the effect of discouraging, delaying,
conditioning, or preventing</div>
<div>access to the Corresponding Resource
constitutes a failure to comply</div>
<div>with the requirements of this License.</div>
<div><br>
</div>
<div> e) You may convey the object code using
peer-to-peer transmission,</div>
<div> provided that you clearly inform all peers
where the object code and</div>
<div> the Corresponding Resource are being
offered to the general public,</div>
<div> free of charge, under the terms of this
License.</div>
<div><br>
</div>
<div>A separable portion of the object code whose
source is excluded from</div>
<div>the Corresponding Resource as a System Library
need not be included in</div>
<div>the transmission of the object code. If you
convey an object code Work</div>
<div>under this Section in, with, or specifically
for use in a User Product,</div>
<div>and the conveyance occurs as part of a
transaction transferring the right</div>
<div>of possession or use of the User Product to the
recipient, the Corresponding</div>
<div>Resource must be accompanied by the
Installation Information. This requirement</div>
<div>does not apply if neither you nor any third
party retains the ability to</div>
<div>install modified object code on the User
Product. The Corresponding Resource</div>
<div>and any Installation Information provided under
this Section must be in a</div>
<div>publicly documented format, must not impose
additional restrictions that</div>
<div>materially limit the practical ability of
recipients to exercise the rights</div>
<div>granted under this License to access, and must
remain available for as long</div>
<div>as necessary to satisfy the requirements of
this License.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>V. Termination.</div>
<div><br>
</div>
<div>You may not convey, or modify a covered Work
except as</div>
<div>expressly permitted under this License. Any
attempt to do so otherwise</div>
<div>is void and shall automatically terminate your
rights under this</div>
<div>License. However, if you cease all violations
of this License, your</div>
<div>rights under this License from a particular
copyright holder are</div>
<div>reinstated provisionally, unless and until that
copyright holder</div>
<div>explicitly and finally terminates those rights.</div>
<div><br>
</div>
<div>Your rights are reinstated permanently if the
copyright holder fails to</div>
<div>notify you of the violation by reasonable means
within sixty (60) days</div>
<div>after the cessation of the violation.</div>
<div><br>
</div>
<div>Additionally, your rights are reinstated
permanently if this is the</div>
<div>first time you have received notice of a
violation of this License from</div>
<div>that copyright holder, and you cure the
violation within thirty (30)</div>
<div>days after receiving such notice.</div>
<div><br>
</div>
<div>Termination of your rights under this Section
does not terminate the</div>
<div>licenses of any parties who have received
copies of the Work, or rights</div>
<div>under this License, from you prior to such
termination.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>VI. Acceptance Not Required for Possession or
Use.</div>
<div><br>
</div>
<div>You are not required to accept this License in
order to receive,</div>
<div>possess, or use a copy of a covered Work. The
mere act of downloading,</div>
<div>receiving, storing, or executing the Work does
not constitute acceptance</div>
<div>of this License.</div>
<div><br>
</div>
<div>Propagation or conveyance of a covered Work
that occurs solely as an</div>
<div>automatic, incidental, or passive consequence
of using a network,</div>
<div>distribution system, or peer-to-peer
transmission to receive a copy</div>
<div>likewise does not require acceptance of this
License.</div>
<div><br>
</div>
<div>However, nothing other than this License grants
you permission to</div>
<div>convey, or modify a covered Work. Any such
actions without</div>
<div>authorization under this License constitute
copyright infringement.</div>
<div><br>
</div>
<div>By propagating, conveying, or modifying a
covered Work, you indicate</div>
<div>your acceptance of this License and all of its
terms and conditions</div>
<div>with respect to those actions.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>VII. Automatic Licensing of Downstream
Recipients.</div>
<div><br>
</div>
<div>The license granted to recipients of a covered
Work arises solely by</div>
<div>operation of this License and not by virtue of
any separate agreement,</div>
<div>contract, or policy.</div>
<div><br>
</div>
<div>Each time you convey a covered Work, the
recipient automatically</div>
<div>receives a license directly from the original
licensors to use,</div>
<div>operate, study, modify, and convey that Work,
subject to the terms and</div>
<div>conditions of this License.</div>
<div><br>
</div>
<div>You are not responsible for enforcing
compliance with this License by</div>
<div>third parties.</div>
<div><br>
</div>
<div>An "entity transaction" means a transaction
that transfers control of</div>
<div>an organization, transfers substantially all of
its assets, subdivides</div>
<div>an organization, or merges organizations. If
conveyance of a covered</div>
<div>Work results from an entity transaction, each
party to that transaction</div>
<div>who receives a copy of the Work also receives
any licenses to the Work</div>
<div>that the predecessor in interest had or could
grant under this License,</div>
<div>together with the right to receive the
Corresponding Resource of the</div>
<div>Work, if the predecessor possesses it or can
obtain it with reasonable</div>
<div>effort.</div>
<div><br>
</div>
<div>You may not impose any additional legal,
contractual, technical, or</div>
<div>policy-based restrictions on the exercise of
the rights granted or</div>
<div>affirmed under this License. Any attempt to
impose such further</div>
<div>restrictions is void and shall not affect the
rights of recipients</div>
<div>under this License.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>VIII. Patents.</div>
<div><br>
</div>
<div>A "Contributor" is a copyright holder who
authorizes the use of a</div>
<div>covered Work under this License. The Work so
licensed is referred to</div>
<div>as the Contributor\u2019s "Contributor Version".</div>
<div><br>
</div>
<div>Each Contributor grants to every recipient of
the Contributor Version</div>
<div>a non-exclusive, worldwide, royalty-free,
irrevocable patent license</div>
<div>under any patent claims owned or controlled by
that Contributor, to</div>
<div>the extent that such claims are necessarily
infringed by the use,</div>
<div>operation, modification, or conveyance of the
Contributor Version in</div>
<div>a manner permitted by this License.</div>
<div><br>
</div>
<div>This patent license applies only to those
patent claims that are</div>
<div>unavoidably infringed by exercising the rights
granted under this</div>
<div>License with respect to the Contributor
Version. It does not extend</div>
<div>to patent claims that would be infringed solely
as a result of further</div>
<div>modification, combination, or use beyond the
scope of the Contributor</div>
<div>Version.</div>
<div><br>
</div>
<div>If you convey a covered Work, you may not rely
on, assert, or enforce</div>
<div>any patent license, agreement, covenant, or
arrangement that would</div>
<div>result in any recipient being denied the full
exercise of the rights</div>
<div>granted under this License.</div>
<div><br>
</div>
<div>Any patent license granted in connection with a
covered Work must be</div>
<div>non-discriminatory and must extend equally to
all recipients of that</div>
<div>Work under this License.</div>
<div><br>
</div>
<div>Nothing in this License shall be construed as
limiting, excluding, or</div>
<div>waiving any implied patent license, patent
exhaustion doctrine, or</div>
<div>other defenses to patent infringement that may
be available under</div>
<div>applicable law.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>IX. Linking and Combined Works.</div>
<div><br>
</div>
<div>A Library Work covered by this License may be
linked, combined, or</div>
<div>otherwise integrated with an independent Work,
whether statically or</div>
<div>dynamically, without causing this License to
apply to the independent</div>
<div>Work as a whole, provided that the terms of
this Section are satisfied.</div>
<div><br>
</div>
<div>The Library Work itself, and any modifications
to it, must remain</div>
<div>licensed under this License. Any party
conveying a modified version of</div>
<div>the Library Work, or a Combined Work containing
a modified Library Work,</div>
<div>must comply with the terms of this License with
respect to the Library</div>
<div>Work.</div>
<div><br>
</div>
<div>You must not restrict the ability of recipients
to modify the Library</div>
<div>Work and to relink or otherwise use a modified
version of the Library</div>
<div>Work with the Combined Work. This includes
providing the necessary</div>
<div>source code, interface information, and build
mechanisms required to</div>
<div>enable such modification and relinking.</div>
<div><br>
</div>
<div>A Combined Work that merely links to, imports,
or uses a Library Work</div>
<div>through its defined interfaces shall not be
required to be licensed</div>
<div>under this License, provided that the Library
Work remains separable</div>
<div>and replaceable.</div>
<div><br>
</div>
<div>Mere aggregation of independent Works, or
communication between</div>
<div>independent Works through standard interfaces,
inter-process</div>
<div>communication, command-line invocation, or
network protocols, does not</div>
<div>by itself cause this License to apply to such
independent Works.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>X. Equal Access to Corresponding Resource.</div>
<div><br>
</div>
<div>Where access to a covered Work or its
Corresponding Resource is granted</div>
<div>to any recipient, such access must be provided
in a manner consistent</div>
<div>with the requirements of this License and must
not impose additional</div>
<div>restrictions that materially and demonstrably
impair the ability of</div>
<div>recipients to exercise the rights granted
herein.</div>
<div><br>
</div>
<div>Differences in timing, format, location, or
method of access shall not</div>
<div>constitute a violation of this License unless
they have the practical</div>
<div>effect of preventing or significantly hindering
recipients from</div>
<div>understanding, modifying, or reusing the Work.</div>
<div><br>
</div>
<div>The Corresponding Resource must be provided in
a form that is reasonably</div>
<div>usable and modifiable by a competent developer
using commonly available</div>
<div>tools.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>XI. Protection of Contributor Rights.</div>
<div><br>
</div>
<div>No agreement, policy, contract, or other
arrangement may retroactively</div>
<div>restrict, revoke, or nullify the rights granted
to a Contributor under</div>
<div>this License with respect to their
contributions.</div>
<div><br>
</div>
<div>Any additional agreement affecting a
Contributor\u2019s contributions must</div>
<div>not diminish the permissions, freedoms, or
protections granted by this</div>
<div>License to that Contributor or to recipients of
the covered Work.</div>
<div><br>
</div>
<div>If conditions are imposed upon you, whether by
court order, agreement,</div>
<div>policy, or otherwise, that contradict the
conditions of this License,</div>
<div>such conditions do not excuse you from
complying with this License. If</div>
<div>you cannot convey a covered Work in a manner
that simultaneously</div>
<div>satisfies your obligations under this License
and any other applicable</div>
<div>obligations, then you may not convey the
covered Work at all.</div>
<div><br>
</div>
<div>You may not impose, accept, or pass through any
obligation that has the</div>
<div>effect of restricting, conditioning, or
discouraging the exercise of</div>
<div>the rights granted under this License by
recipients of the covered Work.</div>
<div>For example, if you agree to terms that require
the collection of fees,</div>
<div>royalties, or other consideration as a
condition of further conveyance,</div>
<div>and such terms are incompatible with this
License, you must refrain</div>
<div>entirely from conveying the covered Work under
those terms.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>XII. Uniform Exercise of Rights.</div>
<div><br>
</div>
<div>Where a covered Work is conveyed, distributed,
or made available in</div>
<div>object code, executable, operational, or
service form, the</div>
<div>Corresponding Resource for that Work must be
made available under this</div>
<div>License no later than the time at which such
form is first provided to</div>
<div>any recipient.</div>
<div><br>
</div>
<div>A difference in timing, manner, or conditions
under which access to the</div>
<div>Work or its Corresponding Resource is provided
shall constitute a</div>
<div>violation of this License only where such
difference materially and</div>
<div>demonstrably prevents recipients from
exercising the rights granted</div>
<div>under this License.</div>
<div><br>
</div>
<div>Nothing in this Section shall be construed to
prohibit staged releases,</div>
<div>differentiated distribution models, or varied
access arrangements,</div>
<div>provided that the Corresponding Resource is
made available in a manner</div>
<div>consistent with the requirements of this
License and without imposing</div>
<div>additional restrictions on the exercise of the
rights granted herein.</div>
<div><br>
</div>
<div>The rights granted under this License apply
equally to all recipients</div>
<div>and all fields of endeavor. No restriction or
condition may be imposed</div>
<div>that limits the exercise of such rights based
on the nature, identity,</div>
<div>or purpose of the recipient.</div>
<div><br>
</div>
<div>The rights granted under this License may not
be negated or restricted</div>
<div>by separate agreements, policies, or
contractual terms to the extent</div>
<div>that such terms conflict with this License.</div>
<div><br>
</div>
<div>Where a covered Work is operated as part of a
larger system, service,</div>
<div>or deployment, the Corresponding Resource shall
include only the source</div>
<div>code of the covered Work itself and any
modifications thereto, and does</div>
<div>not require the disclosure of independent works
or system components</div>
<div>that are not derived from the covered Work.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>XIII. Disclaimer of Warranty.</div>
<div><br>
</div>
<div>TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE
LAW, THE WORK IS PROVIDED</div>
<div>"AS IS" AND WITHOUT WARRANTY OF ANY KIND.
EXCEPT WHERE OTHERWISE</div>
<div>EXPRESSLY STATED IN WRITING, THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES</div>
<div>PROVIDE THE WORK WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING,</div>
<div>BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR</div>
<div>A PARTICULAR PURPOSE, TITLE, OR
NON-INFRINGEMENT. THE ENTIRE RISK AS TO</div>
<div>THE QUALITY, PERFORMANCE, AND FUNCTIONALITY OF
THE WORK IS WITH YOU.</div>
<div>SHOULD THE WORK PROVE DEFECTIVE OR FAIL TO
OPERATE AS EXPECTED, YOU</div>
<div>ASSUME ALL COSTS OF NECESSARY SERVICING,
REPAIR, CORRECTION, OR REMEDIATION.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>XIV. Limitation of Liability.</div>
<div><br>
</div>
<div>TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE
LAW, IN NO EVENT SHALL</div>
<div>ANY COPYRIGHT HOLDER, CONTRIBUTOR, OR ANY OTHER
PARTY WHO MODIFIES,</div>
<div>CONVEYS, OR OTHERWISE MAKES THE WORK AVAILABLE
BE LIABLE TO YOU FOR</div>
<div>ANY DAMAGES OF ANY KIND, INCLUDING, WITHOUT
LIMITATION, DIRECT,</div>
<div>INDIRECT, GENERAL, SPECIAL, INCIDENTAL,
CONSEQUENTIAL, EXEMPLARY, OR</div>
<div>PUNITIVE DAMAGES, ARISING OUT OF OR IN
CONNECTION WITH THE USE OF, OR</div>
<div>INABILITY TO USE, THE WORK, EVEN IF SUCH PARTY
HAS BEEN ADVISED OF THE</div>
<div>POSSIBILITY OF SUCH DAMAGES.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>XV. Interpretation of Sections XIII and XIV.</div>
<div><br>
</div>
<div>If the disclaimer of warranty or limitation of
liability set forth in</div>
<div>Sections XIII and XIV of this License cannot be
given full legal effect</div>
<div>under applicable local law, such provisions
shall be enforced to the</div>
<div>maximum extent permitted by that law.</div>
<div><br>
</div>
<div>In such cases, courts shall apply the local law
in a manner that most</div>
<div>closely approximates an absolute exclusion or
limitation of civil</div>
<div>liability in connection with the Work,
consistent with the intent of</div>
<div>Sections XIII and XIV, unless a warranty or
assumption of liability</div>
<div>accompanies a copy of the Work in return for a
fee.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>-------- PART II \u2014 NETWORK-BASED OPERATION AND
PLATFORM CONSTRAINTS--------</div>
<div>This Part clarifies how the core obligations of
this License apply when ---</div>
<div>a covered Work is operated, deployed, or made
available as part of a ------</div>
<div>network-accessible service or managed system.
THIS PART IS NON-NORMATIVE. -</div>
<div>Nothing in this Part creates additional
permissions, obligations, or ------</div>
<div>restrictions beyond those expressly set forth
in Part I. ------------------</div>
<div>---------------------------------------------------------------------------</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>I. Design Intent and Scope (Non-Normative)</div>
<div><br>
</div>
<div>This License is intentionally designed to
address deployment models</div>
<div>and technical realities that are insufficiently
covered by existing</div>
<div>copyleft licenses, including but not limited
to:</div>
<div><br>
</div>
<div>- Network-based service operation without
distribution</div>
<div>- Managed deployment environments and
platform-controlled systems</div>
<div>- Modern software supply chains involving
orchestration and service glue</div>
<div><br>
</div>
<div>The operative provisions of this License
reflect these goals directly.</div>
<div>This explanatory section is non-normative and
does not modify the legal</div>
<div>terms of the License.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>II. Authority of Interpretation.</div>
<div><br>
</div>
<div>The terms of this License shall be interpreted
according to their</div>
<div>plain meaning and intent, as expressed in the
text of this License,</div>
<div>and in accordance with applicable law. No
person or organization may</div>
<div>grant permissions, exceptions, or
interpretations that purport to</div>
<div>modify the terms of this License or impose
additional obligations</div>
<div>beyond those expressly stated herein, except by
the applicable</div>
<div>copyright holder with respect to their own
contributions.</div>
<div>Any statements, policies, guidance documents,
contractual terms,</div>
<div>or representations not expressly incorporated
into this License</div>
<div>shall have no effect on the scope,
interpretation, or enforcement</div>
<div>of the rights and obligations granted under
this License. Nothing</div>
<div>in this section limits judicial interpretation,
community analysis,</div>
<div>academic commentary, or non-binding explanatory
materials, provided</div>
<div>that such materials do not claim to alter or
supersede the terms of</div>
<div>this License.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>III. Protection of Users\u2019 Legal Rights Against
Technological Measures.</div>
<div><br>
</div>
<div>No covered Work shall be considered part of an
effective technological</div>
<div>measure under Article 11 of the WIPO Copyright
Treaty of 20 December 1996,</div>
<div>or any similar law, to the extent that such a
measure is used primarily</div>
<div>to restrict or prohibit the exercise of rights
granted under this License.</div>
<div><br>
</div>
<div>By licensing, conveying, or otherwise applying
this License to a Work,</div>
<div>you agree not to assert any legal right to
prohibit or restrict the</div>
<div>circumvention of technological measures where
such circumvention is</div>
<div>necessary to exercise the rights granted under
this License.</div>
<div><br>
</div>
<div>This Section does not prohibit the use of
technical mechanisms that are</div>
<div>designed solely to ensure system integrity,
security, authenticity, or</div>
<div>reliable distribution, including but not
limited to secure boot</div>
<div>mechanisms, cryptographic signature
verification, or platform-level</div>
<div>distribution requirements, provided that such
mechanisms do not prevent</div>
<div>recipients from accessing, modifying, or
conveying the Corresponding</div>
<div>Resource of the covered Work under the terms of
this License.</div>
<div><br>
</div>
<div>Any technological, contractual, legal, or
policy-based mechanism that,</div>
<div>in practice, conditions access to the
Corresponding Resource on payment,</div>
<div>exclusive agreements, subscription status,
customer classification, or</div>
<div>acceptance of terms inconsistent with this
License shall be deemed a</div>
<div>technological measure for the purposes of this
Section.</div>
<div><br>
</div>
<div>Platform policies or distribution requirements
that apply uniformly,</div>
<div>without discrimination, and that do not
restrict the availability or</div>
<div>exercise of rights granted under this License
shall not, by themselves,</div>
<div>constitute a violation of this Section.</div>
<div><br>
</div>
<div>---------------------------------------------------------------------------</div>
<div><br>
</div>
<div>IV. Additional Terms.</div>
<div><br>
</div>
<div>Nothing in this License grants permission to
relicense a Work in a</div>
<div>manner not permitted by the terms under which
that Work was originally</div>
<div>licensed.</div>
<div><br>
</div>
<div>"Additional permissions" are terms that
supplement this License by</div>
<div>granting limited exceptions to one or more of
its conditions, without</div>
<div>removing, weakening, or contradicting the core
requirements of this</div>
<div>License.</div>
<div><br>
</div>
<div>Additional permissions that apply to an entire
Work shall be treated</div>
<div>as incorporated into this License with respect
to that Work, to the</div>
<div>extent that they are valid under applicable
law. Where additional</div>
<div>permissions apply only to a specific portion of
a Work, that portion</div>
<div>may be used under those permissions, provided
that the Work as a whole</div>
<div>remains governed by this License.</div>
<div><br>
</div>
<div>When conveying a Work covered by this License,
you are not required to</div>
<div>propagate additional permissions that were
granted by a previous</div>
<div>contributor, unless such permissions are
inseparable from the material</div>
<div>to which they apply. Additional permissions may
also be removed when</div>
<div>modifying the Work, where such removal is
</div></div></div></blockquote></div></div></blockquote></div></blockquote></div></blockquote></div>