License-History.txt 28 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542
  1. License-History.txt
  2. ===================
  3. This file contains the history of license change and contributor's agreement
  4. changes.
  5. Unless otherwise noted in a specific file, the EDK2 project is now licensed
  6. under the terms listed in the License.txt file. Terms under which Contributions
  7. made prior to the move to the License.txt formulation are shown below. Those
  8. terms require notice of the terms themselves be preserved and presented with the
  9. contributions. This file serves that preservation purpose as a matter of
  10. documenting the history of the project.
  11. Key Dates
  12. ----------
  13. * August 3, 2017
  14. Update the TianoCore Contribution Agreement from Version 1.0
  15. to Version 1.1 to cover open source documentation associated
  16. with the TianoCore project.
  17. Version 1.0 covers source code files. Version 1.1 is a
  18. backwards compatible extension that adds support for document
  19. files in both source form and compiled form.
  20. References:
  21. https://opensource.org/licenses/BSD-2-Clause
  22. Complete text of TianoCore Contribution Agreement 1.0 included below
  23. Complete text of TianoCore Contribution Agreement 1.1 included below
  24. Proposals (RFCs):
  25. https://lists.01.org/pipermail/edk2-devel/2017-March/008654.html
  26. TianoCore Bugzilla:
  27. https://bugzilla.tianocore.org/show_bug.cgi?id=629
  28. * April 9, 2019
  29. Replace BSD 2-Clause License with BSD + Patent License removing the need for
  30. the TianoCore Contribution Agreement.
  31. References:
  32. https://opensource.org/licenses/BSD-2-Clause
  33. Complete text of TianoCore Contribution Agreement 1.0 included below
  34. Complete text of TianoCore Contribution Agreement 1.1 included below
  35. https://opensource.org/licenses/BSDplusPatent
  36. Proposals (RFCs):
  37. https://lists.01.org/pipermail/edk2-devel/2019-February/036260.html
  38. https://lists.01.org/pipermail/edk2-devel/2019-March/037500.html
  39. TianoCore Bugzilla:
  40. https://bugzilla.tianocore.org/show_bug.cgi?id=1373
  41. --------------------------------------------------------------------------------
  42. License.txt: BSD 2-Clause License
  43. --------------------------------------------------------------------------------
  44. Redistribution and use in source and binary forms, with or without
  45. modification, are permitted provided that the following conditions
  46. are met:
  47. * Redistributions of source code must retain the above copyright
  48. notice, this list of conditions and the following disclaimer.
  49. * Redistributions in binary form must reproduce the above copyright
  50. notice, this list of conditions and the following disclaimer in
  51. the documentation and/or other materials provided with the
  52. distribution.
  53. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  54. "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
  55. LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
  56. FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
  57. COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
  58. INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
  59. BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  60. LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
  61. CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  62. LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
  63. ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
  64. POSSIBILITY OF SUCH DAMAGE.
  65. --------------------------------------------------------------------------------
  66. --------------------------------------------------------------------------------
  67. Contributions.txt: TianoCore Contribution Agreement 1.1
  68. --------------------------------------------------------------------------------
  69. ======================
  70. = Code Contributions =
  71. ======================
  72. To make a contribution to a TianoCore project, follow these steps.
  73. 1. Create a change description in the format specified below to
  74. use in the source control commit log.
  75. 2. Your commit message must include your "Signed-off-by" signature,
  76. and "Contributed-under" message.
  77. 3. Your "Contributed-under" message explicitly states that the
  78. contribution is made under the terms of the specified
  79. contribution agreement. Your "Contributed-under" message
  80. must include the name of contribution agreement and version.
  81. For example: Contributed-under: TianoCore Contribution Agreement 1.1
  82. The "TianoCore Contribution Agreement" is included below in
  83. this document.
  84. 4. Submit your code to the TianoCore project using the process
  85. that the project documents on its web page. If the process is
  86. not documented, then submit the code on development email list
  87. for the project.
  88. 5. It is preferred that contributions are submitted using the same
  89. copyright license as the base project. When that is not possible,
  90. then contributions using the following licenses can be accepted:
  91. * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause
  92. * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause
  93. * MIT: http://opensource.org/licenses/MIT
  94. * Python-2.0: http://opensource.org/licenses/Python-2.0
  95. * Zlib: http://opensource.org/licenses/Zlib
  96. For documentation:
  97. * FreeBSD Documentation License
  98. https://www.freebsd.org/copyright/freebsd-doc-license.html
  99. Contributions of code put into the public domain can also be
  100. accepted.
  101. Contributions using other licenses might be accepted, but further
  102. review will be required.
  103. =====================================================
  104. = Change Description / Commit Message / Patch Email =
  105. =====================================================
  106. Your change description should use the standard format for a
  107. commit message, and must include your "Signed-off-by" signature
  108. and the "Contributed-under" message.
  109. == Sample Change Description / Commit Message =
  110. === Start of sample patch email message ===
  111. From: Contributor Name <contributor@example.com>
  112. Subject: [Repository/Branch PATCH] Module: Brief-single-line-summary
  113. Full-commit-message
  114. Contributed-under: TianoCore Contribution Agreement 1.1
  115. Signed-off-by: Contributor Name <contributor@example.com>
  116. ---
  117. An extra message for the patch email which will not be considered part
  118. of the commit message can be added here.
  119. Patch content inline or attached
  120. === End of sample patch email message ===
  121. === Notes for sample patch email ===
  122. * The first line of commit message is taken from the email's subject
  123. line following [Repository/Branch PATCH]. The remaining portion of the
  124. commit message is the email's content until the '---' line.
  125. * git format-patch is one way to create this format
  126. === Definitions for sample patch email ===
  127. * "Repository" is the identifier of the repository the patch applies.
  128. This identifier should only be provided for repositories other than
  129. 'edk2'. For example 'edk2-BuildSpecification' or 'staging'.
  130. * "Branch" is the identifier of the branch the patch applies. This
  131. identifier should only be provided for branches other than 'edk2/master'.
  132. For example 'edk2/UDK2015', 'edk2-BuildSpecification/release/1.27', or
  133. 'staging/edk2-test'.
  134. * "Module" is a short identifier for the affected code or documentation. For
  135. example 'MdePkg', 'MdeModulePkg/UsbBusDxe', 'Introduction', or
  136. 'EDK II INF File Format'.
  137. * "Brief-single-line-summary" is a short summary of the change.
  138. * The entire first line should be less than ~70 characters.
  139. * "Full-commit-message" a verbose multiple line comment describing
  140. the change. Each line should be less than ~70 characters.
  141. * "Contributed-under" explicitly states that the contribution is
  142. made under the terms of the contribution agreement. This
  143. agreement is included below in this document.
  144. * "Signed-off-by" is the contributor's signature identifying them
  145. by their real/legal name and their email address.
  146. ========================================
  147. = TianoCore Contribution Agreement 1.1 =
  148. ========================================
  149. INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE, DOCUMENTATION
  150. ("DOCUMENTATION"), INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE
  151. TIANOCORE OPEN SOURCE PROJECT (COLLECTIVELY "CONTENT"). USE OF THE CONTENT
  152. IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND
  153. INTEL AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES
  154. INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR
  155. USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND
  156. CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR
  157. REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
  158. AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
  159. AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
  160. USE THE CONTENT.
  161. Unless otherwise indicated, all Content (except Documentation) made available
  162. on the TianoCore site is provided to you under the terms and conditions of the
  163. BSD License ("BSD"). A copy of the BSD License is available at
  164. http://opensource.org/licenses/bsd-license.php
  165. or when applicable, in the associated License.txt file.
  166. Unless otherwise indicated, all Documentation made available on the
  167. TianoCore site is provided to you under the terms and conditions of the
  168. FreeBSD Documentation License ("FreeBSD"). A copy of the license is
  169. available at https://www.freebsd.org/copyright/freebsd-doc-license.html or,
  170. when applicable, in the associated License.txt file.
  171. Certain other content may be made available under other licenses as
  172. indicated in or with such Content (for example, in a License.txt file).
  173. You accept and agree to the following terms and conditions for Your
  174. present and future Contributions submitted to TianoCore site. Except
  175. for the license granted to Intel hereunder, You reserve all right,
  176. title, and interest in and to Your Contributions.
  177. == SECTION 1: Definitions ==
  178. * "You" or "Contributor" shall mean the copyright owner or legal
  179. entity authorized by the copyright owner that is making a
  180. Contribution hereunder. All other entities that control, are
  181. controlled by, or are under common control with that entity are
  182. considered to be a single Contributor. For the purposes of this
  183. definition, "control" means (i) the power, direct or indirect, to
  184. cause the direction or management of such entity, whether by
  185. contract or otherwise, or (ii) ownership of fifty percent (50%)
  186. or more of the outstanding shares, or (iii) beneficial ownership
  187. of such entity.
  188. * "Contribution" shall mean any original work of authorship,
  189. including any modifications or additions to an existing work,
  190. that is intentionally submitted by You to the TianoCore site for
  191. inclusion in, or documentation of, any of the Content. For the
  192. purposes of this definition, "submitted" means any form of
  193. electronic, verbal, or written communication sent to the
  194. TianoCore site or its representatives, including but not limited
  195. to communication on electronic mailing lists, source code
  196. control systems, and issue tracking systems that are managed by,
  197. or on behalf of, the TianoCore site for the purpose of
  198. discussing and improving the Content, but excluding
  199. communication that is conspicuously marked or otherwise
  200. designated in writing by You as "Not a Contribution."
  201. == SECTION 2: License for Contributions ==
  202. * Contributor hereby agrees that redistribution and use of the
  203. Contribution in source and binary forms, with or without
  204. modification, are permitted provided that the following
  205. conditions are met:
  206. ** Redistributions of source code must retain the Contributor's
  207. copyright notice, this list of conditions and the following
  208. disclaimer.
  209. ** Redistributions in binary form must reproduce the Contributor's
  210. copyright notice, this list of conditions and the following
  211. disclaimer in the documentation and/or other materials provided
  212. with the distribution.
  213. * Disclaimer. None of the names of Contributor, Intel, or the names
  214. of their respective contributors may be used to endorse or
  215. promote products derived from this software without specific
  216. prior written permission.
  217. * Contributor grants a license (with the right to sublicense) under
  218. claims of Contributor's patents that Contributor can license that
  219. are infringed by the Contribution (as delivered by Contributor) to
  220. make, use, distribute, sell, offer for sale, and import the
  221. Contribution and derivative works thereof solely to the minimum
  222. extent necessary for licensee to exercise the granted copyright
  223. license; this patent license applies solely to those portions of
  224. the Contribution that are unmodified. No hardware per se is
  225. licensed.
  226. * EXCEPT AS EXPRESSLY SET FORTH IN SECTION 3 BELOW, THE
  227. CONTRIBUTION IS PROVIDED BY THE CONTRIBUTOR "AS IS" AND ANY
  228. EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
  229. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
  230. PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
  231. CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  232. SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  233. NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  234. LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  235. HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
  236. CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
  237. OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE
  238. CONTRIBUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
  239. DAMAGE.
  240. == SECTION 3: Representations ==
  241. * You represent that You are legally entitled to grant the above
  242. license. If your employer(s) has rights to intellectual property
  243. that You create that includes Your Contributions, You represent
  244. that You have received permission to make Contributions on behalf
  245. of that employer, that Your employer has waived such rights for
  246. Your Contributions.
  247. * You represent that each of Your Contributions is Your original
  248. creation (see Section 4 for submissions on behalf of others).
  249. You represent that Your Contribution submissions include complete
  250. details of any third-party license or other restriction
  251. (including, but not limited to, related patents and trademarks)
  252. of which You are personally aware and which are associated with
  253. any part of Your Contributions.
  254. == SECTION 4: Third Party Contributions ==
  255. * Should You wish to submit work that is not Your original creation,
  256. You may submit it to TianoCore site separately from any
  257. Contribution, identifying the complete details of its source
  258. and of any license or other restriction (including, but not
  259. limited to, related patents, trademarks, and license agreements)
  260. of which You are personally aware, and conspicuously marking the
  261. work as "Submitted on behalf of a third-party: [named here]".
  262. == SECTION 5: Miscellaneous ==
  263. * Applicable Laws. Any claims arising under or relating to this
  264. Agreement shall be governed by the internal substantive laws of
  265. the State of Delaware or federal courts located in Delaware,
  266. without regard to principles of conflict of laws.
  267. * Language. This Agreement is in the English language only, which
  268. language shall be controlling in all respects, and all versions
  269. of this Agreement in any other language shall be for accommodation
  270. only and shall not be binding. All communications and notices made
  271. or given pursuant to this Agreement, and all documentation and
  272. support to be provided, unless otherwise noted, shall be in the
  273. English language.
  274. --------------------------------------------------------------------------------
  275. --------------------------------------------------------------------------------
  276. Contributions.txt: TianoCore Contribution Agreement 1.0
  277. --------------------------------------------------------------------------------
  278. ======================
  279. = Code Contributions =
  280. ======================
  281. To make a contribution to a TianoCore project, follow these steps.
  282. 1. Create a change description in the format specified below to
  283. use in the source control commit log.
  284. 2. Your commit message must include your "Signed-off-by" signature,
  285. and "Contributed-under" message.
  286. 3. Your "Contributed-under" message explicitly states that the
  287. contribution is made under the terms of the specified
  288. contribution agreement. Your "Contributed-under" message
  289. must include the name of contribution agreement and version.
  290. For example: Contributed-under: TianoCore Contribution Agreement 1.0
  291. The "TianoCore Contribution Agreement" is included below in
  292. this document.
  293. 4. Submit your code to the TianoCore project using the process
  294. that the project documents on its web page. If the process is
  295. not documented, then submit the code on development email list
  296. for the project.
  297. 5. It is preferred that contributions are submitted using the same
  298. copyright license as the base project. When that is not possible,
  299. then contributions using the following licenses can be accepted:
  300. * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause
  301. * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause
  302. * MIT: http://opensource.org/licenses/MIT
  303. * Python-2.0: http://opensource.org/licenses/Python-2.0
  304. * Zlib: http://opensource.org/licenses/Zlib
  305. Contributions of code put into the public domain can also be
  306. accepted.
  307. Contributions using other licenses might be accepted, but further
  308. review will be required.
  309. =====================================================
  310. = Change Description / Commit Message / Patch Email =
  311. =====================================================
  312. Your change description should use the standard format for a
  313. commit message, and must include your "Signed-off-by" signature
  314. and the "Contributed-under" message.
  315. == Sample Change Description / Commit Message =
  316. === Start of sample patch email message ===
  317. From: Contributor Name <contributor@example.com>
  318. Subject: [PATCH] CodeModule: Brief-single-line-summary
  319. Full-commit-message
  320. Contributed-under: TianoCore Contribution Agreement 1.0
  321. Signed-off-by: Contributor Name <contributor@example.com>
  322. ---
  323. An extra message for the patch email which will not be considered part
  324. of the commit message can be added here.
  325. Patch content inline or attached
  326. === End of sample patch email message ===
  327. === Notes for sample patch email ===
  328. * The first line of commit message is taken from the email's subject
  329. line following [PATCH]. The remaining portion of the commit message
  330. is the email's content until the '---' line.
  331. * git format-patch is one way to create this format
  332. === Definitions for sample patch email ===
  333. * "CodeModule" is a short idenfier for the affected code. For
  334. example MdePkg, or MdeModulePkg UsbBusDxe.
  335. * "Brief-single-line-summary" is a short summary of the change.
  336. * The entire first line should be less than ~70 characters.
  337. * "Full-commit-message" a verbose multiple line comment describing
  338. the change. Each line should be less than ~70 characters.
  339. * "Contributed-under" explicitely states that the contribution is
  340. made under the terms of the contribtion agreement. This
  341. agreement is included below in this document.
  342. * "Signed-off-by" is the contributor's signature identifying them
  343. by their real/legal name and their email address.
  344. ========================================
  345. = TianoCore Contribution Agreement 1.0 =
  346. ========================================
  347. INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE, DOCUMENTATION,
  348. INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE TIANOCORE OPEN SOURCE
  349. PROJECT (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE
  350. TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND INTEL AND/OR THE
  351. TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR
  352. REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE
  353. CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS
  354. OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
  355. BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
  356. AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
  357. AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
  358. USE THE CONTENT.
  359. Unless otherwise indicated, all Content made available on the TianoCore
  360. site is provided to you under the terms and conditions of the BSD
  361. License ("BSD"). A copy of the BSD License is available at
  362. http://opensource.org/licenses/bsd-license.php
  363. or when applicable, in the associated License.txt file.
  364. Certain other content may be made available under other licenses as
  365. indicated in or with such Content. (For example, in a License.txt file.)
  366. You accept and agree to the following terms and conditions for Your
  367. present and future Contributions submitted to TianoCore site. Except
  368. for the license granted to Intel hereunder, You reserve all right,
  369. title, and interest in and to Your Contributions.
  370. == SECTION 1: Definitions ==
  371. * "You" or "Contributor" shall mean the copyright owner or legal
  372. entity authorized by the copyright owner that is making a
  373. Contribution hereunder. All other entities that control, are
  374. controlled by, or are under common control with that entity are
  375. considered to be a single Contributor. For the purposes of this
  376. definition, "control" means (i) the power, direct or indirect, to
  377. cause the direction or management of such entity, whether by
  378. contract or otherwise, or (ii) ownership of fifty percent (50%)
  379. or more of the outstanding shares, or (iii) beneficial ownership
  380. of such entity.
  381. * "Contribution" shall mean any original work of authorship,
  382. including any modifications or additions to an existing work,
  383. that is intentionally submitted by You to the TinaoCore site for
  384. inclusion in, or documentation of, any of the Content. For the
  385. purposes of this definition, "submitted" means any form of
  386. electronic, verbal, or written communication sent to the
  387. TianoCore site or its representatives, including but not limited
  388. to communication on electronic mailing lists, source code
  389. control systems, and issue tracking systems that are managed by,
  390. or on behalf of, the TianoCore site for the purpose of
  391. discussing and improving the Content, but excluding
  392. communication that is conspicuously marked or otherwise
  393. designated in writing by You as "Not a Contribution."
  394. == SECTION 2: License for Contributions ==
  395. * Contributor hereby agrees that redistribution and use of the
  396. Contribution in source and binary forms, with or without
  397. modification, are permitted provided that the following
  398. conditions are met:
  399. ** Redistributions of source code must retain the Contributor's
  400. copyright notice, this list of conditions and the following
  401. disclaimer.
  402. ** Redistributions in binary form must reproduce the Contributor's
  403. copyright notice, this list of conditions and the following
  404. disclaimer in the documentation and/or other materials provided
  405. with the distribution.
  406. * Disclaimer. None of the names of Contributor, Intel, or the names
  407. of their respective contributors may be used to endorse or
  408. promote products derived from this software without specific
  409. prior written permission.
  410. * Contributor grants a license (with the right to sublicense) under
  411. claims of Contributor's patents that Contributor can license that
  412. are infringed by the Contribution (as delivered by Contributor) to
  413. make, use, distribute, sell, offer for sale, and import the
  414. Contribution and derivative works thereof solely to the minimum
  415. extent necessary for licensee to exercise the granted copyright
  416. license; this patent license applies solely to those portions of
  417. the Contribution that are unmodified. No hardware per se is
  418. licensed.
  419. * EXCEPT AS EXPRESSLY SET FORTH IN SECTION 3 BELOW, THE
  420. CONTRIBUTION IS PROVIDED BY THE CONTRIBUTOR "AS IS" AND ANY
  421. EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
  422. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
  423. PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
  424. CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  425. SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  426. NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  427. LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  428. HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
  429. CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
  430. OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE
  431. CONTRIBUTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
  432. DAMAGE.
  433. == SECTION 3: Representations ==
  434. * You represent that You are legally entitled to grant the above
  435. license. If your employer(s) has rights to intellectual property
  436. that You create that includes Your Contributions, You represent
  437. that You have received permission to make Contributions on behalf
  438. of that employer, that Your employer has waived such rights for
  439. Your Contributions.
  440. * You represent that each of Your Contributions is Your original
  441. creation (see Section 4 for submissions on behalf of others).
  442. You represent that Your Contribution submissions include complete
  443. details of any third-party license or other restriction
  444. (including, but not limited to, related patents and trademarks)
  445. of which You are personally aware and which are associated with
  446. any part of Your Contributions.
  447. == SECTION 4: Third Party Contributions ==
  448. * Should You wish to submit work that is not Your original creation,
  449. You may submit it to TianoCore site separately from any
  450. Contribution, identifying the complete details of its source
  451. and of any license or other restriction (including, but not
  452. limited to, related patents, trademarks, and license agreements)
  453. of which You are personally aware, and conspicuously marking the
  454. work as "Submitted on behalf of a third-party: [named here]".
  455. == SECTION 5: Miscellaneous ==
  456. * Applicable Laws. Any claims arising under or relating to this
  457. Agreement shall be governed by the internal substantive laws of
  458. the State of Delaware or federal courts located in Delaware,
  459. without regard to principles of conflict of laws.
  460. * Language. This Agreement is in the English language only, which
  461. language shall be controlling in all respects, and all versions
  462. of this Agreement in any other language shall be for accommodation
  463. only and shall not be binding. All communications and notices made
  464. or given pursuant to this Agreement, and all documentation and
  465. support to be provided, unless otherwise noted, shall be in the
  466. English language.
  467. --------------------------------------------------------------------------------