VirtualBox

source: vbox/trunk/src/VBox/Devices/EFI/FirmwareNew/License-History.txt@ 99396

Last change on this file since 99396 was 80721, checked in by vboxsync, 5 years ago

Devices/EFI/FirmwareNew: Start upgrade process to edk2-stable201908 (compiles on Windows and works to some extent), bugref:4643

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

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette