SecurityPkg: Add TPM PTP support in TPM2 device lib.

[mirror_edk2.git] / StdLibPrivateInternalFiles / Contributions.txt

diff --git a/StdLibPrivateInternalFiles/Contributions.txt b/StdLibPrivateInternalFiles/Contributions.txt
index 667ca1035ca8486346e3689c0b2b83791e677d0f..f87cbd73c693427ac236e46c99ab92fb68f06b62 100644 (file)
--- a/StdLibPrivateInternalFiles/Contributions.txt
+++ b/StdLibPrivateInternalFiles/Contributions.txt
@@ -19,10 +19,24 @@ To make a contribution to a TianoCore project, follow these steps.
    that the project documents on its web page.  If the process is\r
    not documented, then submit the code on development email list\r
    for the project.\r
+5. It is preferred that contributions are submitted using the same\r
+   copyright license as the base project. When that is not possible,\r
+   then contributions using the following licenses can be accepted:\r
+   * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause\r
+   * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause\r
+   * MIT: http://opensource.org/licenses/MIT\r
+   * Python-2.0: http://opensource.org/licenses/Python-2.0\r
+   * Zlib: http://opensource.org/licenses/Zlib\r
 \r
-=======================================\r
-= Change Description / Commit Message =\r
-=======================================\r
+   Contributions of code put into the public domain can also be\r
+   accepted.\r
+\r
+   Contributions using other licenses might be accepted, but further\r
+   review will be required.\r
+\r
+=====================================================\r
+= Change Description / Commit Message / Patch Email =\r
+=====================================================\r
 \r
 Your change description should use the standard format for a\r
 commit message, and must include your "Signed-off-by" signature\r
@@ -30,7 +44,32 @@ and the "Contributed-under" message.
 \r
 == Sample Change Description / Commit Message =\r
 \r
-=== Definitions for sample change description ===\r
+=== Start of sample patch email message ===\r
+\r
+From: Contributor Name <contributor@example.com>\r
+Subject: [PATCH] CodeModule: Brief-single-line-summary\r
+\r
+Full-commit-message\r
+\r
+Contributed-under: TianoCore Contribution Agreement 1.0\r
+Signed-off-by: Contributor Name <contributor@example.com>\r
+---\r
+\r
+An extra message for the patch email which will not be considered part\r
+of the commit message can be added here.\r
+\r
+Patch content inline or attached\r
+\r
+=== End of sample patch email message ===\r
+\r
+=== Notes for sample patch email ===\r
+\r
+* The first line of commit message is taken from the email's subject\r
+  line following [PATCH]. The remaining portion of the commit message\r
+  is the email's content until the '---' line.\r
+* git format-patch is one way to create this format\r
+\r
+=== Definitions for sample patch email ===\r
 \r
 * "CodeModule" is a short idenfier for the affected code.  For\r
   example MdePkg, or MdeModulePkg UsbBusDxe.\r
@@ -44,15 +83,6 @@ and the "Contributed-under" message.
 * "Signed-off-by" is the contributor's signature identifying them\r
   by their real/legal name and their email address.\r
 \r
-=== Start of sample change description / commit message ===\r
-CodeModule: Brief-single-line-summary\r
-\r
-Full-commit-message\r
-\r
-Contributed-under: TianoCore Contribution Agreement 1.0\r
-Signed-off-by: Contributor Name <contributor@email.server>\r
-=== End of sample change description / commit message ===\r
-\r
 ========================================\r
 = TianoCore Contribution Agreement 1.0 =\r
 ========================================\r