1# Management Policy for Open-Source Compliance Artifacts 2 3## Overview 4When introducing, using, and redistributing third-party open-source software, you must fulfill open-source obligations in the software license. Common open-source obligations are classified into obligations to declare the use of open-source software, obligations to declare the code open-source, and obligations to declare modifications to the code. Deliverables required for fulfilling open-source obligations are collectively referred to as open-source compliance artifacts. This document focuses on the specifications for these artifacts in the OpenHarmony community. 5 6## Managing Artifacts for Declaring the Use of Software 7The common method in the industry for declaring the use of a piece of open-source software is to provide a **NOTICE** file with the version release. The **NOTICE** file specifies the name, copyright, and license information of the open-source software used, as well as a disclaimer. 8 9### Usage Scenarios of NOTICE 10 11If the binary file contains third-party open-source software, provide a file named **NOTICE** to declare the use of the software. 12 13### Requirements on the NOTICE Content 14 15The **NOTICE** file must describe all third-party open-source software used in the code, including their names, software versions, copyrights, and license information in plain text. 16 17### Generation Rules for NOTICE 18 19See [Automatic Generation and Collection Policy of OpenHarmony Open-Source Software NOTICE](https://gitee.com/openharmony/build/blob/master/docs/%E5%BC%80%E6%BA%90%E8%BD%AF%E4%BB%B6Notice%E6%94%B6%E9%9B%86%E7%AD%96%E7%95%A5%E8%AF%B4%E6%98%8E.md). 20 21### Storage Location of NOTICE 22 23#### For OS Device Images 24 25- The **NOTICE** file is stored as **NOTICE.txt** under **system.img > system/etc** in the standard device OS image package ( .tar file). 26 27- The **NOTICE** file is stored as **NOTICE.txt** under **/system/etc** in the system. 28 29#### For Applications 30The **NOTICE** file is usually stored in the top directory of the release folder or compressed package. For a .jar file, the **NOTICE** is generally stored in the **META-INF** directory. 31 32### Lifecycle of NOTICE 33The lifecycle of the **NOTICE** file is the same as that of the binary file. According to the [OpenHarmony Version Lifecycle Rules](https://gitee.com/openharmony/release-management/blob/master/openHarmony-version-lifecycle-management.md), the lifecycle of the **NOTICE** file matches that of the LTS and Release versions. 34 35### NOTICE Template 36 37A complete **NOTICE** file should contain the following content: 38 39``` 40OPEN SOURCE SOFTWARE NOTICE 41 42Please note we provide an open source software notice for the third party open source software along with this software and/or this software component (in the following just "this SOFTWARE"). The open source software licenses are granted by the respective right holders. 43 44Warranty Disclaimer 45THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SEE THE APPLICABLE LICENSES FOR MORE DETAILS. 46 47Copyright Notice and License Texts 48---------------------------------------------------------------------- 49 50Software: XXXX vXX 51 52Copyright notice: 53Copyright 2023 XXXX Co. LTD 54Copyright 2022 XXXX Co. LTD 55License: Apache License 2.0 56 57 Apache License 58 Version 2.0, January 2004 59 http://www.apache.org/licenses/ 60 61 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 62 63 1. Definitions. 64 65 "License" shall mean the terms and conditions for use, reproduction, 66 and distribution as defined by Sections 1 through 9 of this document. 67 68 "Licensor" shall mean the copyright owner or entity authorized by 69 the copyright owner that is granting the License. 70 71 "Legal Entity" shall mean the union of the acting entity and all 72 other entities that control, are controlled by, or are under common 73 control with that entity. For the purposes of this definition, 74 "control" means (i) the power, direct or indirect, to cause the 75 direction or management of such entity, whether by contract or 76 otherwise, or (ii) ownership of fifty percent (50%) or more of the 77 outstanding shares, or (iii) beneficial ownership of such entity. 78 79 "You" (or "Your") shall mean an individual or Legal Entity 80 exercising permissions granted by this License. 81 82 "Source" form shall mean the preferred form for making modifications, 83 including but not limited to software source code, documentation 84 source, and configuration files. 85 86 "Object" form shall mean any form resulting from mechanical 87 transformation or translation of a Source form, including but 88 not limited to compiled object code, generated documentation, 89 and conversions to other media types. 90 91 "Work" shall mean the work of authorship, whether in Source or 92 Object form, made available under the License, as indicated by a 93 copyright notice that is included in or attached to the work 94 (an example is provided in the Appendix below). 95 96 "Derivative Works" shall mean any work, whether in Source or Object 97 form, that is based on (or derived from) the Work and for which the 98 editorial revisions, annotations, elaborations, or other modifications 99 represent, as a whole, an original work of authorship. For the purposes 100 of this License, Derivative Works shall not include works that remain 101 separable from, or merely link (or bind by name) to the interfaces of, 102 the Work and Derivative Works thereof. 103 104 "Contribution" shall mean any work of authorship, including 105 the original version of the Work and any modifications or additions 106 to that Work or Derivative Works thereof, that is intentionally 107 submitted to Licensor for inclusion in the Work by the copyright owner 108 or by an individual or Legal Entity authorized to submit on behalf of 109 the copyright owner. For the purposes of this definition, "submitted" 110 means any form of electronic, verbal, or written communication sent 111 to the Licensor or its representatives, including but not limited to 112 communication on electronic mailing lists, source code control systems, 113 and issue tracking systems that are managed by, or on behalf of, the 114 Licensor for the purpose of discussing and improving the Work, but 115 excluding communication that is conspicuously marked or otherwise 116 designated in writing by the copyright owner as "Not a Contribution." 117 118 "Contributor" shall mean Licensor and any individual or Legal Entity 119 on behalf of whom a Contribution has been received by Licensor and 120 subsequently incorporated within the Work. 121 122 2. Grant of Copyright License. Subject to the terms and conditions of 123 this License, each Contributor hereby grants to You a perpetual, 124 worldwide, non-exclusive, no-charge, royalty-free, irrevocable 125 copyright license to reproduce, prepare Derivative Works of, 126 publicly display, publicly perform, sublicense, and distribute the 127 Work and such Derivative Works in Source or Object form. 128 129 3. Grant of Patent License. Subject to the terms and conditions of 130 this License, each Contributor hereby grants to You a perpetual, 131 worldwide, non-exclusive, no-charge, royalty-free, irrevocable 132 (except as stated in this section) patent license to make, have made, 133 use, offer to sell, sell, import, and otherwise transfer the Work, 134 where such license applies only to those patent claims licensable 135 by such Contributor that are necessarily infringed by their 136 Contribution(s) alone or by combination of their Contribution(s) 137 with the Work to which such Contribution(s) was submitted. If You 138 institute patent litigation against any entity (including a 139 cross-claim or counterclaim in a lawsuit) alleging that the Work 140 or a Contribution incorporated within the Work constitutes direct 141 or contributory patent infringement, then any patent licenses 142 granted to You under this License for that Work shall terminate 143 as of the date such litigation is filed. 144 145 4. Redistribution. You may reproduce and distribute copies of the 146 Work or Derivative Works thereof in any medium, with or without 147 modifications, and in Source or Object form, provided that You 148 meet the following conditions: 149 150 (a) You must give any other recipients of the Work or 151 Derivative Works a copy of this License; and 152 153 (b) You must cause any modified files to carry prominent notices 154 stating that You changed the files; and 155 156 (c) You must retain, in the Source form of any Derivative Works 157 that You distribute, all copyright, patent, trademark, and 158 attribution notices from the Source form of the Work, 159 excluding those notices that do not pertain to any part of 160 the Derivative Works; and 161 162 (d) If the Work includes a "NOTICE" text file as part of its 163 distribution, then any Derivative Works that You distribute must 164 include a readable copy of the attribution notices contained 165 within such NOTICE file, excluding those notices that do not 166 pertain to any part of the Derivative Works, in at least one 167 of the following places: within a NOTICE text file distributed 168 as part of the Derivative Works; within the Source form or 169 documentation, if provided along with the Derivative Works; or, 170 within a display generated by the Derivative Works, if and 171 wherever such third-party notices normally appear. The contents 172 of the NOTICE file are for informational purposes only and 173 do not modify the License. You may add Your own attribution 174 notices within Derivative Works that You distribute, alongside 175 or as an addendum to the NOTICE text from the Work, provided 176 that such additional attribution notices cannot be construed 177 as modifying the License. 178 179 You may add Your own copyright statement to Your modifications and 180 may provide additional or different license terms and conditions 181 for use, reproduction, or distribution of Your modifications, or 182 for any such Derivative Works as a whole, provided Your use, 183 reproduction, and distribution of the Work otherwise complies with 184 the conditions stated in this License. 185 186 5. Submission of Contributions. Unless You explicitly state otherwise, 187 any Contribution intentionally submitted for inclusion in the Work 188 by You to the Licensor shall be under the terms and conditions of 189 this License, without any additional terms or conditions. 190 Notwithstanding the above, nothing herein shall supersede or modify 191 the terms of any separate license agreement you may have executed 192 with Licensor regarding such Contributions. 193 194 6. Trademarks. This License does not grant permission to use the trade 195 names, trademarks, service marks, or product names of the Licensor, 196 except as required for reasonable and customary use in describing the 197 origin of the Work and reproducing the content of the NOTICE file. 198 199 7. Disclaimer of Warranty. Unless required by applicable law or 200 agreed to in writing, Licensor provides the Work (and each 201 Contributor provides its Contributions) on an "AS IS" BASIS, 202 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 203 implied, including, without limitation, any warranties or conditions 204 of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 205 PARTICULAR PURPOSE. You are solely responsible for determining the 206 appropriateness of using or redistributing the Work and assume any 207 risks associated with Your exercise of permissions under this License. 208 209 8. Limitation of Liability. In no event and under no legal theory, 210 whether in tort (including negligence), contract, or otherwise, 211 unless required by applicable law (such as deliberate and grossly 212 negligent acts) or agreed to in writing, shall any Contributor be 213 liable to You for damages, including any direct, indirect, special, 214 incidental, or consequential damages of any character arising as a 215 result of this License or out of the use or inability to use the 216 Work (including but not limited to damages for loss of goodwill, 217 work stoppage, computer failure or malfunction, or any and all 218 other commercial damages or losses), even if such Contributor 219 has been advised of the possibility of such damages. 220 221 9. Accepting Warranty or Additional Liability. While redistributing 222 the Work or Derivative Works thereof, You may choose to offer, 223 and charge a fee for, acceptance of support, warranty, indemnity, 224 or other liability obligations and/or rights consistent with this 225 License. However, in accepting such obligations, You may act only 226 on Your own behalf and on Your sole responsibility, not on behalf 227 of any other Contributor, and only if You agree to indemnify, 228 defend, and hold each Contributor harmless for any liability 229 incurred by, or claims asserted against, such Contributor by reason 230 of your accepting any such warranty or additional liability. 231 232 END OF TERMS AND CONDITIONS 233 234``` 235 236 237## Managing Artifacts for Declaring Code Open-Source 238 239The code released in the OpenHarmony community is automatically open-sourced, and therefore no additional open-source software package is required. The tool described in [Generating an Open-Source Software Package](https://gitee.com/openharmony/build/blob/master/docs/%E7%94%9F%E6%88%90%E5%BC%80%E6%BA%90%E8%BD%AF%E4%BB%B6%E5%8C%85.md) enables automatic generation of the open-source software packages involved in OpenHarmony during the integration of downstream products. It also provides the reference implementation. The OpenHarmony community is not responsible for the fulfillment of open-source obligations of downstream products. 240 241The obligations specified in the license clauses must be fulfilled. For example, the open-source code can be compiled, and the compilation result is consistent with the open-source part in the distributed software artifact; a build guide is included in the open-source software package to describe the build environment, tools, and operation procedures. 242 243 244## Managing Artifacts for Declaring Modifications to Software 245 246According to some open-source license clauses, after modifying a piece of open-source software, you must declare the modification time, modified code, and modified files. 247 248If an existing file of the open-source software is modified, attach the modification statement to the header of the modified file. For details, see the following template. 249 250``` 251* 20XX.XX.XX - XXXXX (modification time and brief description of the modification) 252 Copyright(c)20XX. XXXXXXX (Copyright statement of the modifier, with the year when the modification occurs.) 253``` 254 255If a file is added to the open-source software, attach the copyright statement of the new contributor, license, and disclaimer to the file header.