CONTRIBUTING | 6 +++++- DEVELOPER-CERTIFICATE | 38 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 1 deletion(-) create mode 100644 DEVELOPER-CERTIFICATE
This is a conventional filename for this and makes it more
discoverable. The text is small enough that the copy in
CONTRIBUTING can stay a copy, I think.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
CONTRIBUTING | 6 +++++-
DEVELOPER-CERTIFICATE | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644 DEVELOPER-CERTIFICATE
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 6ec146baf0..923d1a89d6 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -61,7 +61,11 @@ Developer's Certificate of Origin
All patches to the Xen Project code base must include the line
"Signed-off-by: your_name <your_email>" at the end of the change
description. This is required and indicates that you certify the patch
-under the "Developer's Certificate of Origin" which states:
+under the "Developer's Certificate of Origin".
+
+The declaration you are making with your Signed-off-by can be
+found in xen.git in the file DEVELOPER-CERTIFICATE. For your
+convenience, here is the operative part:
Developer's Certificate of Origin 1.1
diff --git a/DEVELOPER-CERTIFICATE b/DEVELOPER-CERTIFICATE
new file mode 100644
index 0000000000..912d22ee9e
--- /dev/null
+++ b/DEVELOPER-CERTIFICATE
@@ -0,0 +1,38 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+ have the right to submit it under the open source license
+ indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+ of my knowledge, is covered under an appropriate open source
+ license and I have the right under that license to submit that
+ work with modifications, whether created in whole or in part
+ by me, under the same open source license (unless I am
+ permitted to submit under a different license), as indicated
+ in the file; or
+
+(c) The contribution was provided directly to me by some other
+ person who certified (a), (b) or (c) and I have not modified
+ it.
+
+(d) I understand and agree that this project and the contribution
+ are public and that a record of the contribution (including all
+ personal information I submit with it, including my sign-off) is
+ maintained indefinitely and may be redistributed consistent with
+ this project or the open source license(s) involved.
+
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 02/01/2020 15:16, Ian Jackson wrote: > This is a conventional filename for this Really? Citation definitely needed, because neither Google nor Github can find a single example matching this. Linux has its sole copy in Documentation/process/submitting-patches.rst so ours living in CONTRIBUTING seems perfectly reasonable. I don't think duplicating this an improvement, and I don't see an issue with how we've currently got things arranged. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
© 2016 - 2024 Red Hat, Inc.