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