<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I am reporting that at the Board Meeting on September 15, 2023,
the Board voted not to approve the YATeam Public License Version
1.<br>
<br>
Best regards,<br>
Pamela Chestek<br>
Chair, License Commitee<br>
Open Source Initiative <br>
</p>
<div class="moz-cite-prefix">On 6/13/2022 1:52 PM, Pamela Chestek
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:aadb7893-8f82-7493-bdc3-82ba8267e566@opensource.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
To the License-review list:<br>
<br>
The License Committee recommendation to the Board and the
Rationale Document on the YATeam Public License Version 1 is
below. The Board will be voting on the license at its next board
meeting.<br>
<br>
Pamela Chestek<br>
Open Source Initiative<br>
Chair, License Committee<br>
<br>
===============<br>
<br>
License: YATeam Public License Version 1 (Exhibit A)<br>
Submitted: 21 March 2022,
<a class="moz-txt-link-freetext"
href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2022-March/005223.html"
moz-do-not-send="true">http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2022-March/005223.html</a><br>
Decision date: due no later than the first Board meeting after 21
May 2022<br>
<br>
License Review Committee Recommendation: <br>
<br>
<i>Resolved that it is the opinion of the OSI that the YATeam
Public License Version 1 does not conform to the OSD and assure
software freedom and the license is therefore not approved.</i><br>
<br>
Rationale Document<br>
<br>
This license is an attempt to create a license where the licensor
can choose what options to invoke. However, in Section 4 the
license allows adding restrictions that do not comply with the
OSD, e.g., limiting distribution, limiting the creation of
derivative works, and restricting use commercially. Unless a
license meets the OSD in every possible iteration, it cannot be
approved as an open source license.<br>
<br>
The license is also unintelligible in the English language
version.<br>
<br>
Exhibit A<br>
<br>
本许可证以中英文双语表述 -- THIS LICENSE IS WRITTEN IN BOTH CHINESE AND
ENGLISH<br>
*开始许可证文本*<br>
<br>
**序言**<br>
YATeam公共许可证是一个免费的、copyleft的许可证，用于软件和其他类型的作品。<br>
YATeam发现，尽管许多开源许可证都注重于保护特定群体的权利，但是它们都忽视了一个基本的权利，即许可证使用者自己选择许可证规定的限制的权利，这导致了繁多的许可证出现，进而导致许可证使用者每次选择许可证时都需要再次权衡每个许可证规定的限制是否适合自己的作品。<br>
相较于其他的许可证，YATeam公共许可证更倾向于在尽可能地保障作者与贡献者的权利下，更多地保障作者对于许可证限制的选择权。<br>
复制、使用、修改及分发受YATeam公共许可证（以下简称“本许可证”）的如下条款的约束：<br>
**条款和条件**<br>
**0.定义**<br>
"版权"也指适用于其他类型作品（如半导体掩码）的类似版权的法律。<br>
<br>
"作品"是指根据本许可证许可的任何受版权保护的作品，包括最初“作者”许可在“本许可证”下的作品及后续“贡献者”许可在“本许可证”下的“衍生作品”。<br>
<br>
"作者"是指将受版权保护的作品许可在“本许可证”下的个人或组织。<br>
<br>
"衍生作品"是指基于“作品”创作的作品，具体包括对全部或部分“作品”进行修改、重写、翻译、注释、组合或与之链接（包括动态链接或静态链接）而形成的作品。仅与“作品”进行进程间通信或系统调用的作品是独立作品，不属于“衍生作品”。<br>
<br>
"贡献者"是指基于“作品”创作出“衍生作品”的个人或组织。<br>
<br>
“对应源代码”
是指生成、安装和(对于可执行作品)运行目标代码所需的所有源文件和与之关联的接口定义文件，以及控制这些活动的脚本，但不包括编译环境、编译工具、云平台（如果有）。<br>
<br>
"分发"是指通过任何媒介向他人提供“作品”或“衍生作品”的行为，以及利用“作品”或“衍生作品”通过网络远程给用户提供服务的行为，例如：通过利用“作品”或“衍生作品”搭建的云平台提供在线服务的行为。<br>
<br>
"研究成果"是在未构成“分发”行为的前提下，通过运行修改或未修改的“作品”或“衍生作品”等方式，得出并发布的含部分或不含“作品”或“衍生作品”内容的成果。<br>
<br>
**1.基本权限**<br>
根据本许可证授予的所有权利均在“作品”或“衍生作品”的版权期限内授予，并且在满足所述条件的情况下不可撤销。本许可证明确确认您无限制地允许运行未经修改的程序。仅当分发（鉴于其内容）构成涵盖的“衍生作品”时，运行所涵盖“作品”或“衍生作品”的分发才受本许可证的约束。本许可证承认您的合理使用权或版权法规定的其他同等权利。<br>
您可以在不构成“分发”行为的条件下不受本许可证约束地进行研究，但如果您需要发布“研究成果”或进行“分发”，则受到本许可证的约束。<br>
<br>
**2.无商标许可**<br>
“作者”或“贡献者”在“本许可证”下不提供对其商品名称、商标、服务标识或产品名称的商标许可，但您为满足第3条规定的声明义务而必须使用的情形除外。<br>
<br>
**3.基本的义务**<br>
您可以将您接收到的“作品”，“衍生作品”或您的“作品”，“衍生作品”以源程序形式或可执行形式“分发”，但必须满足下列条件：<br>
(1)您必须向接收者提供“本许可证”的副本，并且：<br>
(i)如果您是“作品”的“作者”，您需要参照第4.1条进行操作；<br>
(ii)如果您是创作“衍生作品”的“贡献者”，您需要参照第4.2条进行操作；<br>
(2)您必须确保参照第4条创建，编辑并随“本许可证”副本一同“分发”命名为“YPLLIMIT”的文件（以下简称“限制”）。<br>
<br>
**4.权限的分配**<br>
“作者”需要在“作品”的根目录创建命名为“YPLLIMIT”的文件，“作者”与“贡献者”需遵循下列条款进行编辑。<br>
###### 4.1“作者”的权限分配<br>
1.您需要在“限制”中提供以下基本信息：<br>
(1)您的“作品”名称；<br>
(2)您的邮箱；<br>
(3)可以获取您的“作品”的方式（必须保证有效期在“限制”最后编辑完毕之日起不少于三年，并确保接收者可以免费取得“作品”的源代码）；<br>
(4)您最后编辑完毕“限制”的日期。<br>
2.您可以选择在“限制”中选择对于“贡献者”的权限，包括：<br>
(1)分发许可（如果没有此条，接收者不得“分发”此“作品”）；<br>
(2)衍生许可（如果没有此条，接收者不得基于此“作品”创作并“分发”“衍生作品”）；<br>
(3)无版权许可（如果没有此条，“作品”中的版权信息必须保留，“衍生作品”中需保留“作品”的版权，“衍生作品”的“贡献者”有权决定是否写入自己的版权，如果“贡献者”在保留已有版权信息的同时写入自己的版权，“衍生作品”的“衍生作品”必须保留上游“衍生作品”的版权）；<br>
(4)闭源许可（如果没有此条，“贡献者”必须提供“衍生作品”的源代码并随“衍生作品”一同“分发”）；<br>
(5)商用许可（如果没有此条，不得将“作品”及其“衍生作品”商用）；<br>
(6)无限制许可（如果没有此条，“限制”对“作品”与“衍生作品”的约束始终有效）。<br>
###### 4.2“贡献者”的权限分配<br>
您无权更改“作品”或“衍生作品”中“限制”文件的原有内容，包括“衍生作品”的“贡献者”新增内容。您可以新增以下内容：<br>
(1)您的“衍生作品”名称；<br>
(2)您的署名；<br>
(3)您的邮箱；<br>
(4)可以获取您的“衍生作品”的方式（必须保证有效期在“限制”最后编辑完毕之日起不少于三年，并确保接收者可以在不违背第4.1条内容的情况下取得“作品”）；<br>
(5)您最后编辑完毕“限制”的日期。<br>
您必须在“分发”您的“衍生作品”时一同发布编辑过的“限制”文件。但如果您获得“作者”基于第4.1条的不发布源代码许可，您可以不“分发”该“限制”文件，但您仍受其约束。如果您获得“作者”基于第4.1条的商用许可，您可以不“分发”该“限制”文件，但您仍受其约束。<br>
<br>
**5.附加条款与说明**<br>
###### 5.1附加条款<br>
1.如果“作者”在发布最初的“作品”后修改了“限制”，则“限制”最后修改之日后的接收者均受新的“限制”约束，最后修改日之前的接收者均受接收“作品”或“衍生作品”之日时发布的“限制”约束，但此后“分发”则均受新的“限制”约束。所有新的“限制”发布前“分发”的“衍生作品”均受该“衍生作品”“分发”之日时发布的“限制”约束；<br>
2.如果“作者”或“贡献者”需要通过物理介质（如光盘，U盘，硬盘等）向接收者提供“作品”或“衍生作品”，则该“作品”的“作者”或该“衍生作品”的“贡献者”有权向接收者收取费用。<br>
###### 5.2说明<br>
1.如果“作者”在“限制”中添加了第4.1条中的(6)，则如果添加了其他约束，则该约束自动失效，但“作品”与“衍生作品”均仍受“本许可证”约束；<br>
2.如果“作者”在“限制”中添加了第4.1条中的(4)和/或(5)，且没有添加(3)，则接收者必须提供版权查询方式，例如，通过命令"show
-c"输出版权信息；对于GUI页面，可以通过“关于”页面展示版权信息；<br>
3.如果“作者”在“限制”中没有添加第4.1条中的(4)，则无论有无第4.1条中的(5)，均需提供“衍生作品”源代码。对于商业产品，仅需提供“作品”或“衍生作品”的源代码即可；<br>
4.“限制”中“作者”编辑部分如果有以下冲突情况，则“限制”自动失效。在“作者”作出修改前的所有“分发”均需保留版权信息，除此之外不保留任何“限制”所规定的限制。但“作者”修改“限制”且不造成冲突后，修改完毕后的所有接收者均受最后修改的“限制”约束，修改完毕前的接收者需重新获取“限制”并受约束。冲突如下：<br>
(1)“限制”文件中(1)与任意约束并存；<br>
(2)“限制”文件中(2)与(4)并存。<br>
<br>
**6.违约与终止**<br>
如果您违反“本许可证”，您将暂时不得“分发”“作品”或“衍生作品”，且不得自行创作并“分发”“衍生作品”，“本许可证”赋予您的所有权利自动终止，直至您停止所有违反“本许可证”的活动，可以暂时恢复在“限制”约束下的权利。“作者”和/或任何“贡献者”有权通过某种合理途径通知您终止其根据“本许可证”授予您的许可。该“作者”和/或“贡献者”授予您的许可自您接到其终止通知之日起终止。仅在如下两种情形下，即使您收到“作者”和/或“贡献者”的通知也并不终止其授予您的许可：<br>
1.您在接到该终止通知之前已停止所有违反行为；<br>
2.您是首次收到该“作者”和/或“贡献者”根据“本许可证”通过某种合理途径发出的终止通知，并且您在收到该通知后30天内已停止所有违反行为。<br>
如果您的下游接收者遵守“本许可证”的规定，即使您在“本许可证”下被授予的许可终止，不影响下游的接收者根据“本许可证”享有的权利。但在您的权利被终止后仍接收您“分发”的已终止您的权利的“作品”或“衍生作品”的接收者，同样自动终止根据“本许可证”享有的权利。仅在您停止所有违反行为并恢复您的权利后自动恢复该接收者的所有权利。<br>
<br>
**7.自动许可**<br>
每次您转达涵盖的“作品”或“衍生作品”时，接收者都会自动收到原始许可方的许可，以运行、修改和传播该“作品”或“衍生作品”，但须遵守“本许可证”。您不得强制第三方遵守“本许可证”。<br>
您不得对行使根据“本许可证”授予或确认的权利施加任何进一步的限制。例如：您不得在“限制”中加入其他的约束，不得将收取许可费等其他费用作为换取约束的条件。<br>
<br>
**8. 免责声明与责任限制**<br>
“作品”和“衍生作品”在提供时不带有任何明示或默示的担保。在任何情况下，“作者”或“贡献者”或版权人不对任何人因使用“作品”和/或“衍生作品”而引发的任何直接或间接损失承担任何责任，不论该等损失因何种原因导致或者基于何种法律理论,即使其曾被告知有该等损失的可能性。<br>
<br>
**9.语言**<br>
“本许可证”以中英文双语表述，中英文版本具有同等法律效力。如果中英文版本存在任何不一致，以中文版为准。<br>
<br>
**条款结束**<br>
<br>
**如何将YATeam公共许可证，第1版，应用到您的软件**<br>
如果您希望将YATeam公共许可证，第1版，应用到您的软件，为了方便接收者查阅，建议您完成如下步骤：<br>
请将以下通知附加到程序中。最安全的方法是将它们附加到每个源文件的开头，以最有效地声明保修的排除；并且每个文件至少应具有"版权"行和指向完整通知位置的指针。<br>
<br>
```txt<br>
Copyright (c) [Year] [name of copyright holder]<br>
[Software Name] is licensed under YATeam PubL v1.<br>
You can use this software according to the terms and conditions of
the YATeam PubL v1.<br>
You may obtain a copy of YATeam PubL v1 at:<br>
<a class="moz-txt-link-freetext"
href="https://license.yateam.cc/ypl-1.0/" moz-do-not-send="true">https://license.yateam.cc/ypl-1.0/</a><br>
THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES
OF ANY KIND,<br>
EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
NON-INFRINGEMENT,<br>
MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.<br>
See the YATeam PubL v1 for more details.<br>
```<br>
<br>
除此之外，您还需要在软件包的一级目录下创建以“LICENSE”为名的文件，将整个许可证文本放入该文件中，并且在同一目录下按照“本许可证”的要求创建并编辑以“YPLLIMIT”为名的文件。<br>
<br>
*结束许可证文本*<br>
<br>
**Preamble**<br>
The YATeam Public License is a free, copyleft license for software
and other kinds of works.<br>
YATeam found that although many open source licenses focus on
protecting the rights of specific groups, they all ignore a basic
right, that is, the right of license users to choose the
restrictions specified in the license, which leads to the
emergence of a large number of licenses, which leads to the need
for license users to weigh again whether the restrictions
specified in each license are suitable for their works every time
they choose a license.<br>
Compared with other licenses, YATeam Public License tends to
protect the rights of authors and contributors as much as
possible, and protect the authors' choice of license restrictions.<br>
Reproduction, use, modification and distribution are subject to
the following terms of the YATeam Public License (hereinafter
referred to as "this license"):<br>
<br>
**TERMS AND CONDITIONS**<br>
**0.Definitions.**<br>
"Copyright" also means copyright-like laws that apply to other
kinds of Works, such as semiconductor masks.<br>
<br>
"Works" means any copyrighted work licensed under this License,
including the works licensed under this license by the original
Author and the "derivative work" licensed under this License by
subsequent Contributors.<br>
<br>
"Author" refers to the individual or organization that licenses
the copyrighted work under this License.<br>
<br>
"Derivative Works" refers to Works created based on the Works,
specifically including Works formed by modifying, rewriting,
translating, annotating, combining or linking with all or part of
the Works (including dynamic links or static links). Works that
only carry out inter process communication or system call with
Works are independent works and do not belong to Derivative works.<br>
<br>
"Contributor" refers to the individual or organization who creates
Derivative Works based on the Works.<br>
<br>
"Corresponding Source Code" refers to all source files and
associated interface definition files required for generating,
installing and (for executable Works) running object code, as well
as scripts controlling these activities, but does not include
compilation environment, compilation tools and cloud platform (if
any).<br>
<br>
"Distribute(or Distribution)" refers to the act of providing Works
or Derivative Works to others through any media, and the act of
using Works or Derivative Works to provide services to users
remotely through the network, such as providing online services
through the cloud platform built by Works or Derivative Works.<br>
<br>
"Research results" refers to the results with or without the
content of Works or Derivative Works obtained and published by
running modified or unmodified Works or Derivative Works" without
constituting the behavior of Distribution.<br>
<br>
**1.Basic Permissions.**<br>
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running
a covered work is covered by this License only if the output,
given its content, constitutes a covered work. This License
acknowledges your rights of fair use or other equivalent, as
provided by copyright law.<br>
You may conduct research without being bound by this License
without constituting a Distribution behavior, but if you need to
publish Research Results or Distribute, you are bound by this
License.<br>
<br>
**2.No Trademark License.**<br>
The Author or Contributor does not provide a trademark license for
its trade name, trademark, service mark or product name under this
License, except when you must use it to meet your declaration
obligations in Section 3.<br>
<br>
**3.Basic Obligations.**<br>
You can Distribute your received Works, Derivative Works or your
Works and Derivative Works in the form of source program or
executable form, but the following conditions must be met:<br>
(1)You must provide the recipient with a copy of this License and:<br>
(i)If you are the Author of the Works, you need to refer to
Section 4.1;<br>
(ii)if you are a Contributor to the creation of Derivative Works,
you need to refer to section 4.2;<br>
(2)You must ensure that the file named YPLLIMIT (hereinafter
referred to as "Restrictions") is created, edited and Distribute
with the copy of this License with reference to Section 4.<br>
<br>
**4.Allocation of Permissions.**<br>
Author needs to create a file named "YPLLIMIT" in the root
directory of Works, and Author and Contributor need to edit
according to the following terms.<br>
###### 4.1 Permissions Allocation of Authors.<br>
1.You need to provide the following basic information in
Restrictions:<br>
(1) Your Works name;<br>
(2) Your email address;<br>
(3) How to obtain your Works (it must be guaranteed that the
validity period is no less than three years from the date when the
Restrictions is last edited, and the recipient can obtain the
source code of the Work free of charge);<br>
(4) The date when you last edited the "Restrictions".<br>
2.You can select the permissions for Contributor in Restrictions,
including:<br>
(1) DISTRIBUTIONS LICENSE (without this clause, the recipient
shall not Distribute the Work);<br>
(2) DERIVATIVE LICENSE (without this clause, the recipient shall
not create and Distribute Derivative Works based on the works);<br>
(3) NO COPYRIGHT LICENSE (without this clause, the copyright
information in the Works must be retained, the copyright of the
Works must be retained in the Derivative Work, and the Contributor
of the Derivative work has the right to decide whether to write
his own copyright. If the Contributor writes his own copyright
while retaining the existing copyright information, the Derivative
work of the Derivative work must retain the copyright of the
upstream Derivative work);<br>
(4) CLOSED SOURCE LICENSE (without this clause, Contributor must
provide the Corresponding Source Code of Derivative Works and
Distribute with Derivative Works);<br>
(5) COMMERCIAL LICENSE (without this clause, the Works and its
Derivative Works shall not be used commercially);<br>
(6) UNRESTRICIED LICENSE (without this clause, the Restrictions on
the Works and Derivative Works is always valid).<br>
###### 4.2 Permissions Allocation of Contributor.<br>
You have no right to change the original content of the
Restrictions file in the Works or Derivative Works, including the
new content of the Contributor of the Derivative Works. You can
add the following:<br>
(1) The name of your Derivative Works;<br>
(2) Your signature;<br>
(3) Your email address;<br>
(4) The way in which you can obtain your Derivative Works (it must
be guaranteed that the validity period is no less than three years
from the date when the Restrictions is last edited, and ensure
that the recipient can obtain the Works without violating the
contents of Section 4.1);<br>
(5) The date when you last edited the Restrictions.<br>
You must publish the edited Restrictions file with the
Distribution of your Derivative Works. However, if you obtain the
Author's permission not to publish source code based on Section
4.1, you may not Distribute the Restrictions file, but you are
still bound by it. If you obtain a COMMERCIAL LICENSE from the
Author based on Section 4.1, you may not Distribute the
Restrictions file, but you are still bound by it.<br>
<br>
**5.Additional Terms and Instructions.**<br>
###### 5.1 Additional Terms.<br>
1.If the Author modifies the Restrictions after publishing the
original Works, the recipients after the date of the last
modification of the Restrictions are subject to the new
Restrictions, and the recipients before the date of the last
modification are subject to the Restrictions published on the date
of receiving the Works or Derivative Works, but the subsequent
Distribution is subject to the new Restrictions. All Derivative
Works Distributed before the release of the new Restrictions are
subject to the Restrictions published on the date of the
Distribution of the Derivative Works;<br>
2.If the Author or Contributor needs to provide the Works or
Derivative Works to the recipient through physical media (such as
optical disc, USB flash disk, hard disk, etc.), the Author of the
Works or the Contributor of the Derivative Works has the right to
charge the recipient.<br>
###### 5.2 Instructions.<br>
1.If the Author adds (6) in Section 4.1 to the Restrictions with
other restrictions at the same time, the Restrictions will
automatically expire, but the Works" and Derivative Works are
still subject to this License";<br>
2.If the Author adds (4) and / or (5) in Section 4.1 to the
Restrictions and does not add (3), the recipient must provide the
copyright query method, for example, output the copyright
information through the command "show - c"; For GUI pages,
copyright information can be displayed through the About page;<br>
3.If the Author does not add (4) in Section 4.1 to the
Restrictions, the Corresponding Source Code of Derivative Works
shall be provided whether there is (5) in Section 4.1 or not. For
commercial products, you only need to provide the Corresponding
Source Code of Works or Derivative Works;<br>
4.If there are the following conflicts in the editing part of
Author in Restrictions, the Restrictions will automatically become
invalid. All Distributions before the Author makes changes shall
retain the copyright information. In addition, no Restrictions
specified in Restrictions shall be retained. However, after the
Author modifies the Restrictions without causing conflict, all
recipients after the modification are bound by the Restrictions of
the last modification, and the recipients before the modification
need to obtain the Restrictions again and be bound. Conflicts are
as follows:<br>
(1) coexist with any constraint in the Restrictions file;<br>
(2) and (4) coexist in the Restrictions file.<br>
<br>
**6.Breach and Termination.**<br>
If you violate this License, you will not be allowed to Distribute
the Works or Werivative Works temporarily, and you will not be
allowed to create and Distribute the Derivative Works. All rights
granted to you by this License will automatically terminate until
you stop all activities in violation of this License, and you can
temporarily restore your rights under the Restrictions. The Author
and / or any Contributor has the right to terminate the license
granted to you under this License by giving you reasonable notice.
The license granted to you by the Author and / or Contributor is
terminated from the date you receive its termination notice. The
permission granted to you by the Author and / or Contributor will
not be terminated even if you receive the notice from the Author
and / or Contributor only in the following two cases:<br>
1.You have stopped all violations before receiving the termination
notice;<br>
2.This is the first time that you have received a termination
notice from the Author and / or Contributor in some reasonable way
under this License, and you have stopped all violations within 30
days after receiving the notice.<br>
If your downstream recipient complies with the provisions of this
License, the termination of the license granted to you under this
License will not affect the rights of the downstream recipient
under this License. However, the recipient of the Works or
Derivative Works that still receives your Distribution after the
termination of your rights will also automatically terminate the
rights under this License. All rights of the recipient will be
automatically restored only after you stop all violations and
restore your rights.<br>
<br>
**7.Automatic license.**<br>
Each time you convey the covered Works or Derivative Works, the
recipient will automatically receive permissions from the original
licensor to run, modify and disseminate the Works or Derivative
Works, subject to this License. You may not force a third party to
comply with this License.<br>
You may not impose any further Restrictions on the exercise of the
rights granted or confirmed under this License. For example, you
may not add other restrictions to the Restrictions and may not
take the collection of license fees and other fees as a condition
in exchange for restrictions.<br>
<br>
**8.Disclaimer and Limitation of Liability.**<br>
WORKS AND DERIVATIVE WORKS ARE PROVIDED WITHOUT ANY EXPRESS OR
IMPLIED WARRANTY. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTOR OR
COPYRIGHT OWNER BE LIABLE FOR ANY DIRECT OR INDIRECT LOSS INCURRED
BY ANY PERSON DUE TO THE USE OF THE WORK AND / OR DERIVATIVE
WORKS, REGARDLESS OF THE CAUSE OR LEGAL THEORY, EVEN IF HE OR SHE
HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH LOSS.<br>
<br>
**9.Language.**<br>
This License is expressed in both Chinese and English, and the
Chinese and English versions have the same legal effect. In case
of any inconsistency between the Chinese and English versions, the
Chinese version shall prevail.<br>
<br>
**END OF THE TERMS AND CONDITIONS**<br>
<br>
**How to apply the YATeam Public License，Version 1 (YAT PubL v1),
to your software**<br>
To do so, attach the following notices to the program. It is
safest to attach them to the start of each source file to most
effectively state the exclusion of warranty; and each file should
have at least the “copyright” line and a pointer to where the full
notice is found.<br>
```txt<br>
Copyright (c) [Year] [name of copyright holder]<br>
[Software Name] is licensed under YATeam PubL v1.<br>
You can use this software according to the terms and conditions of
the YATeam PubL v1.<br>
You may obtain a copy of YATeam PubL v1 at:<br>
<a class="moz-txt-link-freetext"
href="https://license.yateam.cc/ypl-1.0/" moz-do-not-send="true">https://license.yateam.cc/ypl-1.0/</a><br>
THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES
OF ANY KIND,<br>
EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
NON-INFRINGEMENT,<br>
MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.<br>
See the YATeam PubL v1 for more details.<br>
```<br>
<br>
In addition, you also need to create a file named "LICENSE" in the
first level directory of the software package, put the whole
license text into the file, and create and edit a file named
"YPLLIMIT" in the same directory according to the requirements of
this License.<br>
<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/21/2022 12:41 AM, Forever☆七夜草°
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:tencent_F55E8B6BBE2C02CC5860E90BFD2994B1C305@qq.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div>本许可证以中英文双语表述 -- THIS LICENSE IS WRITTEN IN BOTH CHINESE AND
ENGLISH</div>
<div>*开始许可证文本*</div>
<div><br>
</div>
<div>**序言**</div>
<div>YATeam公共许可证是一个免费的、copyleft的许可证，用于软件和其他类型的作品。</div>
<div>YATeam发现，尽管许多开源许可证都注重于保护特定群体的权利，但是它们都忽视了一个基本的权利，即许可证使用者自己选择许可证规定的限制的权利，这导致了繁多的许可证出现，进而导致许可证使用者每次选择许可证时都需要再次权衡每个许可证规定的限制是否适合自己的作品。</div>
<div>相较于其他的许可证，YATeam公共许可证更倾向于在尽可能地保障作者与贡献者的权利下，更多地保障作者对于许可证限制的选择权。</div>
<div>复制、使用、修改及分发受YATeam公共许可证（以下简称“本许可证”）的如下条款的约束：</div>
<div>**条款和条件**</div>
<div>**0.定义**</div>
<div>"版权"也指适用于其他类型作品（如半导体掩码）的类似版权的法律。</div>
<div><br>
</div>
<div>"作品"是指根据本许可证许可的任何受版权保护的作品，包括最初“作者”许可在“本许可证”下的作品及后续“贡献者”许可在“本许可证”下的“衍生作品”。</div>
<div><br>
</div>
<div>"作者"是指将受版权保护的作品许可在“本许可证”下的个人或组织。</div>
<div><br>
</div>
<div>"衍生作品"是指基于“作品”创作的作品，具体包括对全部或部分“作��”进行修改、重写、翻译、注释、组合或与之链接（包括动态链接或静态链接）而形成的作品。仅与“作品”进行进程间通信或系统调用的作品是独立作品，不属于“衍生作品”。</div>
<div><br>
</div>
<div>"贡献者"是指基于“作品”创作出“衍生作品”的个人或组织。</div>
<div><br>
</div>
<div>“对应源代码”
是指生成、安装和(对于可执行作品)运行目标代码所需的所有源文件和与之关联的接口定义文件，以及控制这些活动的脚本，但不包括编译环境、编译工具、云平台（如果有）。</div>
<div><br>
</div>
<div>"分发"是指通过任何媒介向他人提供“作品”或“衍生作品”的行为，以及利用“作品”或“衍生作品”通过网络远程给用户提供服务的行为，例如：通过利用“作品”或“衍生作品”搭建的云平台提供在线服务的行为。</div>
<div><br>
</div>
<div>"研究成果"是在未构成“分发”行为的前提下，通过运行修改或未修改的“作品”或“衍生作品”等方式，得出并发布的含部分或不含“作品”或“衍生作品”内容的成果。</div>
<div><br>
</div>
<div>**1.基本权限**</div>
<div>根据本许可证授予的所有权利均在“作品”或“衍生作品”的版权期限内授予，并且在满足所述条件的情况下不可撤销。本许可证明确确认您无限制地允许运行未经修改的程序。仅当分发（鉴于其内容）构成涵盖的“衍生作品”时，运行所涵盖“作品”或“衍生作品”的分发才受本许可证的约束。本许可证承认您的合理使用权或版权法规定的其他同等权利。</div>
<div>您可以在不构成“分发”行为的条件下不受本许可证约束地进行研究，但如果您需要发布“研究成果”或进行“分发”，则受到本许可证的约束。</div>
<div><br>
</div>
<div>**2.无商标许可**</div>
<div>“作者”或“贡献者”在“本许可证”下不提供对其商品名称、商标、服务标识或产品名称的商标许可，但您为满足第3条规定的声明义务而必须使用的情形除外。</div>
<div><br>
</div>
<div>**3.基本的义务**</div>
<div>您可以将您接收到的“作品”，“衍生作品”或您的“作品”，“衍生作品”以源程序形式或可执行形式“分发”，但必须满足下列条件：</div>
<div>(1)您必须向接收者提供“本许可证”的副本，并且：</div>
<div>(i)如果您是“作品”的“作者”，您需要参照第4.1条进行操作；</div>
<div>(ii)如果您是创作“衍生作品”的“贡献者”，您需要参照第4.2条进行操作；</div>
<div>(2)您必须确保参照第4条创建，编辑并随“本许可证”副本一同“分发”命名为“YPLLIMIT”的文件（以下简称“限制”）。</div>
<div><br>
</div>
<div>**4.权限的分配**</div>
<div>“作者”需要在“作品”的根目录创建命名为“YPLLIMIT”的文件，“作者”与“贡献者”需遵循下列条款进行编辑。</div>
<div>###### 4.1“作者”的权限分配</div>
<div>1.您需要在“限制”中提供以下基本信息：</div>
<div>(1)您的“作品”名称；</div>
<div>(2)您的邮箱；</div>
<div>(3)可以获取您的“作品”的方式（必须保证有效期在“限制”最后编辑完毕之日起不少于三年，并确保接收者可以免费取得“作品”的源代码）；</div>
<div>(4)您最后编辑完毕“限制”的日期。</div>
<div>2.您可以选择在“限制”中选择对于“贡献者”的权限，包括：</div>
<div>(1)分发许可（如果没有此条，接收者不得“分发”此“作品”）；</div>
<div>(2)衍生许可（如果没有此条，接收者不得基于此“作品”创作并“分发”“衍生作品”）；</div>
<div>(3)无版权许可（如果没有此条，“作品”中的版权信息必须保留，“衍生作品”中需保留“作品”的版权，“衍生作品”的“贡献者”有权决定是否写入自己的版权，如果“贡献者”在保留已有版权信息的同时写入自己的版权，“衍生作品”的“衍生作品”必须保留上游“衍生作品”的版权）；</div>
<div>(4)闭源许可（如果没有此条，“贡献者”必须提供“衍生作品”的源代码并随“衍生作品”一同“分发”）；</div>
<div>(5)商用许可（如果没有此条，不得将“作品”及其“衍生作品”商用）；</div>
<div>(6)无限制许可（如果没有此条，“限制”对“作品”与“衍生作品”的约束始终有效）。</div>
<div>###### 4.2“贡献者”的权限分配</div>
<div>您无权更改“作品”或“衍生作品”中“限制”文件的原有内容，包括“衍生作品”的“贡献者”新增内容。您可以新增以下内容：</div>
<div>(1)您的“衍生作品”名称；</div>
<div>(2)您的署名；</div>
<div>(3)您的邮箱；</div>
<div>(4)可以获取您的“衍生作品”的方式（必须保证有效期在“限制”最后编辑完毕之日起不少于三年，并确保接收者可以在不违背第4.1条内容的情况下取得“作品”）；</div>
<div>(5)您最后编辑完毕“限制”的日期。</div>
<div>您必须在“分发”您的“衍生作品”时一同发布编辑过的“限制”文件。但如果您获得“作者”基于第4.1条的不发布源代码许可，您可以不“分发”该“限制”文件，但您仍受其约束。如果您获得“作者”基于第4.1条的商用许可，您可以不“分发”该“限制”文件，但您仍受其约束。</div>
<div><br>
</div>
<div>**5.附加条款与说明**</div>
<div>###### 5.1附加条款</div>
<div>1.如果“作者”在发布最初的“作品”后修改了“限制”，则“限制”最后修改之日后的接收者均受新的“限制”约束，最后修改日之前的接收者均受接收“作品”或“衍生作品”之日时发布的“限制”约束，但此后“分发”则均受新的“限制”约束。所有新的“限制”发布前“分发”的“衍生作品”均受该“衍生作品”“分发”之日时发布的“限制”约束；</div>
<div>2.如果“作者”或“贡献者”需要通过物理介质（如光盘，U盘，硬盘等）向接收者提供“作品”或“衍生作品”，则该“作品”的“作者”或该“衍生作品”的“贡献者”有权向接收者收取费用。</div>
<div>###### 5.2说明</div>
<div>1.如果“作者”在“限制”中添加了第4.1条中的(6)，则如果添加了其他约束，则该约束自动失效，但“作品”与“衍生作品”均仍受“本许可证”约束；</div>
<div>2.如果“作者”在“限制”中添加了第4.1条中的(4)和/或(5)，且没有添加(3)，则接收者必须提供版权查询方式，例如，通过命令"show
-c"输出版权信息；对于GUI页面，可以通过“关于”页面展示版权信息；</div>
<div>3.如果“作者”在“限制”中没有添加第4.1条中的(4)，则无论有无第4.1条中的(5)，均需提供“衍生作品”源代码。对于商业产品，仅需提供“作品”或“衍生作品”的源代码即可；</div>
<div>4.“限制”中“作者”编辑部分如果有以下冲突情况，则“限制”自动失效。在“作者”作出修改前的所有“分发”均需保留版权信息，除此之外不保留任何“限制”所规定的限制。但“作者”修改“限制”且不造成冲突后，修改完毕后的所有接收者均受最后修改的“限制”约束，修改完毕前的接收者需重新获取“限制”并受约束。冲突如下：</div>
<div>(1)“限制”文件中(1)与任意约束并存；</div>
<div>(2)“限制”文件中(2)与(4)并存。</div>
<div><br>
</div>
<div>**6.违约与终止**</div>
<div>如果您违反“本许可证”，您将暂时不得“分发”“作品”或“衍生作品”，且不得自行创作并“分发”“衍生作品”，“本许可证”赋予您的所有权利自动终止，直至您停止所有违反“本许可证”的活动，可以暂时恢复在“限制”约束下的权利。“作者”和/或任何“贡献者”有权通过某种合理途径通知您终止其根据“本许可证”授予您的许可。该“作者”和/或“贡献者”授予您的许可自您接到其终止通知之日起终止。仅在如下两种情形下，即使您收到“作者”和/或“贡献者”的通知也并不终止其授予您的许可：</div>
<div>1.您在接到该终止通知之前已停止所有违反行为；</div>
<div>2.您是首次收到该“作者”和/或“贡献者”根据“本许可证”通过某种合理途径发出的终止通知，并且您在收到该通知后30天内已停止所有违反行为。</div>
<div>如果您的下游接收者遵守“本许可证”的规定，即使您在“本许可证”下被授予的许可终止，不影响下游的接收者根据“本许可证”享有的权利。但在您的权利被终止后仍接收您“分发”的已终止您的权利的“作品”或“衍生作品”的接收者，同样自动终止根据“本许可证”享有的权利。仅在您停止所有违反行为并恢复您的权利后自动恢复该接收者的所有权利。</div>
<div><br>
</div>
<div>**7.自动许可**</div>
<div>每次您转达涵盖的“作品”或“衍生作品”时，接收者都会自动收到原始许可方的许可，以运行、修改和传播该“作品”或“衍生作品”，但须遵守“本许可证”。您不得强制第三方遵守“本许可证”。</div>
<div>您不得对行使根据“本许可证”授予或确认的权利施加任何进一步的限制。例如：您不得在“限制”中加入其他的约束，不得将收取许可费等其他费用作为换取约束的条件。</div>
<div><br>
</div>
<div>**8. 免责声明与责任限制**</div>
<div>“作品”和“衍生作品”在提供时不带有任何明示或默示的担保。在任何情况下，“作者”或“贡献者”或版权人不对任何人因使用“作品”和/或“衍生作品”而引发的任何直接或间接损失承担任何责任，不论该等损失因何种原因导致或者基于何种法律理论,即使其曾被告知有该等损失的可能性。</div>
<div><br>
</div>
<div>**9.语言**</div>
<div>“本许可证”以中英文双语表述，中英文版本具有同等法律效力。如果中英文版本存在任何不一致，以中文版为准。</div>
<div><br>
</div>
<div>**条款结束**</div>
<div><br>
</div>
<div>**如何将YATeam公共许可证，第1版，应用到您的软件**</div>
<div>如果您希望将YATeam公共许可证，第1版，应用到您的软件，为了方便接收者查阅，建议您完成如下步骤：</div>
<div>请将以下通知附加到程序中。最安全的方法是将它们附加到每个源文件的开头，以最有效地声明保修的排除；并且每个文件至少应具有"版权"行和指向完整通知位置的指针。</div>
<div><br>
</div>
<div>```txt</div>
<div>Copyright (c) [Year] [name of copyright holder]</div>
<div>[Software Name] is licensed under YATeam PubL v1.</div>
<div>You can use this software according to the terms and
conditions of the YATeam PubL v1.</div>
<div>You may obtain a copy of YATeam PubL v1 at:</div>
<div><a class="moz-txt-link-freetext"
href="https://license.yateam.cc/ypl-1.0/"
moz-do-not-send="true">https://license.yateam.cc/ypl-1.0/</a></div>
<div>THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
WARRANTIES OF ANY KIND,</div>
<div>EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
NON-INFRINGEMENT,</div>
<div>MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.</div>
<div>See the YATeam PubL v1 for more details.</div>
<div>```</div>
<div><br>
</div>
<div>除此之外，您还需要在软件包的一级目录下创建以“LICENSE”为名的文件，将整个许可证文本放入该文件中，并且在同一目录下按照“本许可证”的要求创建并编辑以“YPLLIMIT”为名的文件。</div>
<div><br>
</div>
<div>*结束许可证文本*</div>
<div><br>
</div>
<div>
<div>**Preamble**</div>
<div>The YATeam Public License is a free, copyleft license for
software and other kinds of works.</div>
<div>YATeam found that although many open source licenses
focus on protecting the rights of specific groups, they all
ignore a basic right, that is, the right of license users to
choose the restrictions specified in the license, which
leads to the emergence of a large number of licenses, which
leads to the need for license users to weigh again whether
the restrictions specified in each license are suitable for
their works every time they choose a license.</div>
<div>Compared with other licenses, YATeam Public License tends
to protect the rights of authors and contributors as much as
possible, and protect the authors' choice of license
restrictions.</div>
<div>Reproduction, use, modification and distribution are
subject to the following terms of the YATeam Public License
(hereinafter referred to as "this license"):</div>
<div><br>
</div>
<div>**TERMS AND CONDITIONS**</div>
<div>**0.Definitions.**</div>
<div>"Copyright" also means copyright-like laws that apply to
other kinds of Works, such as semiconductor masks.</div>
<div><br>
</div>
<div>"Works" means any copyrighted work licensed under this
License, including the works licensed under this license by
the original Author and the "derivative work" licensed under
this License by subsequent Contributors.</div>
<div><br>
</div>
<div>"Author" refers to the individual or organization that
licenses the copyrighted work under this License.</div>
<div><br>
</div>
<div>"Derivative Works" refers to Works created based on the
Works, specifically including Works formed by modifying,
rewriting, translating, annotating, combining or linking
with all or part of the Works (including dynamic links or
static links). Works that only carry out inter process
communication or system call with Works are independent
works and do not belong to Derivative works.</div>
<div><br>
</div>
<div>"Contributor" refers to the individual or organization
who creates Derivative Works based on the Works.</div>
<div><br>
</div>
<div>"Corresponding Source Code" refers to all source files
and associated interface definition files required for
generating, installing and (for executable Works) running
object code, as well as scripts controlling these
activities, but does not include compilation environment,
compilation tools and cloud platform (if any).</div>
<div><br>
</div>
<div>"Distribute(or Distribution)" refers to the act of
providing Works or Derivative Works to others through any
media, and the act of using Works or Derivative Works to
provide services to users remotely through the network, such
as providing online services through the cloud platform
built by Works or Derivative Works.</div>
<div><br>
</div>
<div>"Research results" refers to the results with or without
the content of Works or Derivative Works obtained and
published by running modified or unmodified Works or
Derivative Works" without constituting the behavior of
Distribution.</div>
<div><br>
</div>
<div>**1.Basic Permissions.**</div>
<div>All rights granted under this License are granted for the
term of copyright on the Program, and are irrevocable
provided the stated conditions are met. This License
explicitly affirms your unlimited permission to run the
unmodified Program. The output from running a covered work
is covered by this License only if the output, given its
content, constitutes a covered work. This License
acknowledges your rights of fair use or other equivalent, as
provided by copyright law.</div>
<div>You may conduct research without being bound by this
License without constituting a Distribution behavior, but if
you need to publish Research Results or Distribute, you are
bound by this License.</div>
<div><br>
</div>
<div>**2.No Trademark License.**</div>
<div>The Author or Contributor does not provide a trademark
license for its trade name, trademark, service mark or
product name under this License, except when you must use it
to meet your declaration obligations in Section 3.</div>
<div><br>
</div>
<div>**3.Basic Obligations.**</div>
<div>You can Distribute your received Works, Derivative Works
or your Works and Derivative Works in the form of source
program or executable form, but the following conditions
must be met:</div>
<div>(1)You must provide the recipient with a copy of this
License and:</div>
<div>(i)If you are the Author of the Works, you need to refer
to Section 4.1;</div>
<div>(ii)if you are a Contributor to the creation of
Derivative Works, you need to refer to section 4.2;</div>
<div>(2)You must ensure that the file named YPLLIMIT
(hereinafter referred to as "Restrictions") is created,
edited and Distribute with the copy of this License with
reference to Section 4.</div>
<div><br>
</div>
<div>**4.Allocation of Permissions.**</div>
<div>Author needs to create a file named "YPLLIMIT" in the
root directory of Works, and Author and Contributor need to
edit according to the following terms.</div>
<div>###### 4.1 Permissions Allocation of Authors.</div>
<div>1.You need to provide the following basic information in
Restrictions:</div>
<div>(1) Your Works name;</div>
<div>(2) Your email address;</div>
<div>(3) How to obtain your Works (it must be guaranteed that
the validity period is no less than three years from the
date when the Restrictions is last edited, and the recipient
can obtain the source code of the Work free of charge);</div>
<div>(4) The date when you last edited the "Restrictions".</div>
<div>2.You can select the permissions for Contributor in
Restrictions, including:</div>
<div>(1) DISTRIBUTIONS LICENSE (without this clause, the
recipient shall not Distribute the Work);</div>
<div>(2) DERIVATIVE LICENSE (without this clause, the
recipient shall not create and Distribute Derivative Works
based on the works);</div>
<div>(3) NO COPYRIGHT LICENSE (without this clause, the
copyright information in the Works must be retained, the
copyright of the Works must be retained in the Derivative
Work, and the Contributor of the Derivative work has the
right to decide whether to write his own copyright. If the
Contributor writes his own copyright while retaining the
existing copyright information, the Derivative work of the
Derivative work must retain the copyright of the upstream
Derivative work);</div>
<div>(4) CLOSED SOURCE LICENSE (without this clause,
Contributor must provide the Corresponding Source Code of
Derivative Works and Distribute with Derivative Works);</div>
<div>(5) COMMERCIAL LICENSE (without this clause, the Works
and its Derivative Works shall not be used commercially);</div>
<div>(6) UNRESTRICIED LICENSE (without this clause, the
Restrictions on the Works and Derivative Works is always
valid).</div>
<div>###### 4.2 Permissions Allocation of Contributor.</div>
<div>You have no right to change the original content of the
Restrictions file in the Works or Derivative Works,
including the new content of the Contributor of the
Derivative Works. You can add the following:</div>
<div>(1) The name of your Derivative Works;</div>
<div>(2) Your signature;</div>
<div>(3) Your email address;</div>
<div>(4) The way in which you can obtain your Derivative Works
(it must be guaranteed that the validity period is no less
than three years from the date when the Restrictions is last
edited, and ensure that the recipient can obtain the Works
without violating the contents of Section 4.1);</div>
<div>(5) The date when you last edited the Restrictions.</div>
<div>You must publish the edited Restrictions file with the
Distribution of your Derivative Works. However, if you
obtain the Author's permission not to publish source code
based on Section 4.1, you may not Distribute the
Restrictions file, but you are still bound by it. If you
obtain a COMMERCIAL LICENSE from the Author based on Section
4.1, you may not Distribute the Restrictions file, but you
are still bound by it.</div>
<div><br>
</div>
<div>**5.Additional Terms and Instructions.**</div>
<div>###### 5.1 Additional Terms.</div>
<div>1.If the Author modifies the Restrictions after
publishing the original Works, the recipients after the date
of the last modification of the Restrictions are subject to
the new Restrictions, and the recipients before the date of
the last modification are subject to the Restrictions
published on the date of receiving the Works or Derivative
Works, but the subsequent Distribution is subject to the new
Restrictions. All Derivative Works Distributed before the
release of the new Restrictions are subject to the
Restrictions published on the date of the Distribution of
the Derivative Works;</div>
<div>2.If the Author or Contributor needs to provide the Works
or Derivative Works to the recipient through physical media
(such as optical disc, USB flash disk, hard disk, etc.), the
Author of the Works or the Contributor of the Derivative
Works has the right to charge the recipient.</div>
<div>###### 5.2 Instructions.</div>
<div>1.If the Author adds (6) in Section 4.1 to the
Restrictions with other restrictions at the same time, the
Restrictions will automatically expire, but the Works" and
Derivative Works are still subject to this License";</div>
<div>2.If the Author adds (4) and / or (5) in Section 4.1 to
the Restrictions and does not add (3), the recipient must
provide the copyright query method, for example, output the
copyright information through the command "show - c"; For
GUI pages, copyright information can be displayed through
the About page;</div>
<div>3.If the Author does not add (4) in Section 4.1 to the
Restrictions, the Corresponding Source Code of Derivative
Works shall be provided whether there is (5) in Section 4.1
or not. For commercial products, you only need to provide
the Corresponding Source Code of Works or Derivative Works;</div>
<div>4.If there are the following conflicts in the editing
part of Author in Restrictions, the Restrictions will
automatically become invalid. All Distributions before the
Author makes changes shall retain the copyright information.
In addition, no Restrictions specified in Restrictions shall
be retained. However, after the Author modifies the
Restrictions without causing conflict, all recipients after
the modification are bound by the Restrictions of the last
modification, and the recipients before the modification
need to obtain the Restrictions again and be bound.
Conflicts are as follows:</div>
<div>(1) coexist with any constraint in the Restrictions file;</div>
<div>(2) and (4) coexist in the Restrictions file.</div>
<div><br>
</div>
<div>**6.Breach and Termination.**</div>
<div>If you violate this License, you will not be allowed to
Distribute the Works or Werivative Works temporarily, and
you will not be allowed to create and Distribute the
Derivative Works. All rights granted to you by this License
will automatically terminate until you stop all activities
in violation of this License, and you can temporarily
restore your rights under the Restrictions. The Author and /
or any Contributor has the right to terminate the license
granted to you under this License by giving you reasonable
notice. The license granted to you by the Author and / or
Contributor is terminated from the date you receive its
termination notice. The permission granted to you by the
Author and / or Contributor will not be terminated even if
you receive the notice from the Author and / or Contributor
only in the following two cases:</div>
<div>1.You have stopped all violations before receiving the
termination notice;</div>
<div>2.This is the first time that you have received a
termination notice from the Author and / or Contributor in
some reasonable way under this License, and you have stopped
all violations within 30 days after receiving the notice.</div>
<div>If your downstream recipient complies with the provisions
of this License, the termination of the license granted to
you under this License will not affect the rights of the
downstream recipient under this License. However, the
recipient of the Works or Derivative Works that still
receives your Distribution after the termination of your
rights will also automatically terminate the rights under
this License. All rights of the recipient will be
automatically restored only after you stop all violations
and restore your rights.</div>
<div><br>
</div>
<div>**7.Automatic license.**</div>
<div>Each time you convey the covered Works or Derivative
Works, the recipient will automatically receive permissions
from the original licensor to run, modify and disseminate
the Works or Derivative Works, subject to this License. You
may not force a third party to comply with this License.</div>
<div>You may not impose any further Restrictions on the
exercise of the rights granted or confirmed under this
License. For example, you may not add other restrictions to
the Restrictions and may not take the collection of license
fees and other fees as a condition in exchange for
restrictions.</div>
<div><br>
</div>
<div>**8.Disclaimer and Limitation of Liability.**</div>
<div>WORKS AND DERIVATIVE WORKS ARE PROVIDED WITHOUT ANY
EXPRESS OR IMPLIED WARRANTY. IN NO EVENT SHALL THE AUTHOR OR
CONTRIBUTOR OR COPYRIGHT OWNER BE LIABLE FOR ANY DIRECT OR
INDIRECT LOSS INCURRED BY ANY PERSON DUE TO THE USE OF THE
WORK AND / OR DERIVATIVE WORKS, REGARDLESS OF THE CAUSE OR
LEGAL THEORY, EVEN IF HE OR SHE HAS BEEN INFORMED OF THE
POSSIBILITY OF SUCH LOSS.</div>
<div><br>
</div>
<div>**9.Language.**</div>
<div>This License is expressed in both Chinese and English,
and the Chinese and English versions have the same legal
effect. In case of any inconsistency between the Chinese and
English versions, the Chinese version shall prevail.</div>
<div><br>
</div>
<div>**END OF THE TERMS AND CONDITIONS**</div>
<div><br>
</div>
<div>**How to apply the YATeam Public License，Version 1 (YAT
PubL v1), to your software**</div>
<div>To do so, attach the following notices to the program. It
is safest to attach them to the start of each source file to
most effectively state the exclusion of warranty; and each
file should have at least the “copyright” line and a pointer
to where the full notice is found.</div>
<div>```txt</div>
<div>Copyright (c) [Year] [name of copyright holder]</div>
<div>[Software Name] is licensed under YATeam PubL v1.</div>
<div>You can use this software according to the terms and
conditions of the YATeam PubL v1.</div>
<div>You may obtain a copy of YATeam PubL v1 at:</div>
<div><a class="moz-txt-link-freetext"
href="https://license.yateam.cc/ypl-1.0/"
moz-do-not-send="true">https://license.yateam.cc/ypl-1.0/</a></div>
<div>THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT
WARRANTIES OF ANY KIND,</div>
<div>EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
NON-INFRINGEMENT,</div>
<div>MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE.</div>
<div>See the YATeam PubL v1 for more details.</div>
<div>```</div>
<div><br>
</div>
<div>In addition, you also need to create a file named
"LICENSE" in the first level directory of the software
package, put the whole license text into the file, and
create and edit a file named "YPLLIMIT" in the same
directory according to the requirements of this License.</div>
<div><br>
</div>
<div>*End License Text.*</div>
</div>
<div><br>
</div>
<div>The following are not part of the license:</div>
<div>The website is not available now. We will open the website
after the license approval.</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 moz-txt-link-freetext" href="mailto:License-review@lists.opensource.org" moz-do-not-send="true">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" moz-do-not-send="true">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</blockquote>
</body>
</html>