From nobody Tue Apr 30 22:48:37 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28
as permitted sender) client-ip=209.132.183.28;
envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com;
Authentication-Results: mx.zohomail.com;
spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass(p=none dis=none) header.from=redhat.com
Return-Path:
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by
mx.zohomail.com
with SMTPS id 1528225373765913.2232733959021;
Tue, 5 Jun 2018 12:02:53 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com
[10.5.11.15])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by mx1.redhat.com (Postfix) with ESMTPS id 1C7D4C04BD26;
Tue, 5 Jun 2018 19:02:51 +0000 (UTC)
Received: from colo-mx.corp.redhat.com
(colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20])
by smtp.corp.redhat.com (Postfix) with ESMTPS id 21AE15B680;
Tue, 5 Jun 2018 19:02:50 +0000 (UTC)
Received: from lists01.pubmisc.prod.ext.phx2.redhat.com
(lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33])
by colo-mx.corp.redhat.com (Postfix) with ESMTP id A14021800C9D;
Tue, 5 Jun 2018 19:02:47 +0000 (UTC)
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com
[10.11.54.6])
by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
id w55J2ijn006491 for ;
Tue, 5 Jun 2018 15:02:44 -0400
Received: by smtp.corp.redhat.com (Postfix)
id 45DDE2166BB3; Tue, 5 Jun 2018 19:02:44 +0000 (UTC)
Received: from dnr.brq.redhat.com (ovpn-204-80.brq.redhat.com [10.40.204.80])
by smtp.corp.redhat.com (Postfix) with ESMTP id AB6EB2166BB2
for ; Tue, 5 Jun 2018 19:02:43 +0000 (UTC)
From: =?UTF-8?q?J=C3=A1n=20Tomko?=
To: libvir-list@redhat.com
Date: Tue, 5 Jun 2018 21:02:40 +0200
Message-Id:
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6
X-loop: libvir-list@redhat.com
Subject: [libvirt] [PATCH] docs: document mandatory signoffs in
governance.html
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.12
Precedence: junk
List-Id: Development discussions about the libvirt library & tools
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Sender: libvir-list-bounces@redhat.com
Errors-To: libvir-list-bounces@redhat.com
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
X-Greylist: Sender IP whitelisted,
not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]);
Tue, 05 Jun 2018 19:02:52 +0000 (UTC)
X-ZohoMail: RSF_0 Z_629925259 SPT_0
Amend the paragraphs about no CLAs and implicit license
agreements to mention mandatory Signed-off-by tags.
Signed-off-by: J=C3=A1n Tomko
Reviewed-by: Daniel P. Berrang=C3=A9
---
This is duplicating information, but I did not find a reasonable
way to link the numbered list in hacking.html without making it
look ugly. Very probably due to my lack of trying.
docs/governance.html.in | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/docs/governance.html.in b/docs/governance.html.in
index df5999c0f2..e9608f673c 100644
--- a/docs/governance.html.in
+++ b/docs/governance.html.in
@@ -141,13 +141,17 @@
than having the interest and ability to provide a contribution. The
libvirt project does not require any
"Contributor License Agreement"
- to be signed prior to engagement with the community.
+ to be signed prior to engagement with the community. However for
+ contributing patches, providing a 'Signed-off-by' line with the
+ author's legal name and e-mail address to demonstrate agreement
+ and compliance with the
+ Developer Certificate of Origin is required.
=20
- In making a contribution to the project, the community member is
- implicitly stating that they accept the terms of the license under
- which the work they are contributing to is distributed. They are
+ In making a non-patch contribution to the project, the community
+ member is implicitly stating that they accept the terms of the licen=
se
+ under which the work they are contributing to is distributed. They a=
re
also implicitly stating that they have the legal right to make the
contribution, if doing so on behalf of a broader organization /
company. Most of the project's code is distributed under the GNU
--=20
2.13.6
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list