From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BE31AC76196 for ; Mon, 10 Apr 2023 19:50:22 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id DD7CF42BCA for ; Mon, 10 Apr 2023 19:50:21 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id AD2F19863A4 for ; Mon, 10 Apr 2023 19:50:21 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 9781998631E; Mon, 10 Apr 2023 19:50:21 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 1FB9D986321 for ; Mon, 10 Apr 2023 19:49:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: y2QhPdzlPpC3OJ23uAK_zQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681156165; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=q8O4xAWy9OLkX9SUJtHXe2lZ18P9NhBb+pkmHv2V0Lo=; b=0JWen7JaEJrfmOOJhT7e5F9mZCWbMrOMPpL4FJ/K8DDcsbifs8vA/ssXdqzOuI0gtk 7MPk8pOet+ep82fWO5PmWNvZMSB1FwBBkc6rE71bsWhIeIIQDTt8owqvKWt7Z91QVBcg I5BceAqUDd2Emk9WbyotCvmfA4GDTGTFJYvj9VvVYHPk71SpQiXVVMmJcOx+f20U6QwD DVDkCYLR7NfJMwkVWhZ4ojVVTqXgWJ6ikJ08EW5SjXdWkhPwSbQFg/zeHuulsjXUNRLM Raa6liip0lSIMWQNlxMYprtwksXZgzE/jLhOZv0sOII7RqPTLgcQHxmW/eykZY8ZikBi EAaQ== X-Gm-Message-State: AAQBX9ce95aHcYxzNbYeDZpSyDY8pcM1Fj4QU30fIpmudbCVv8fkzP4N EyoREcSqGHB+RE9poa3Wz/8EoWUdFF4+0yk2R9g+Oh/MZKh5JIy26eh3bZpuNdh8tjTtSr7vNLd 4JRUHUeJEjjlch2d0La6u6b0FoijBEMAVHQ== X-Received: by 2002:adf:db43:0:b0:2ef:b31b:337c with SMTP id f3-20020adfdb43000000b002efb31b337cmr8677714wrj.37.1681156165492; Mon, 10 Apr 2023 12:49:25 -0700 (PDT) X-Google-Smtp-Source: AKy350YA3X9usOVz27xsNwnwIK/HNwBa7/o60Zr3U+ve2aSTGXYPm23tBlQo7sx1ZuyHCQNIQmImVg== X-Received: by 2002:adf:db43:0:b0:2ef:b31b:337c with SMTP id f3-20020adfdb43000000b002efb31b337cmr8677705wrj.37.1681156165139; Mon, 10 Apr 2023 12:49:25 -0700 (PDT) Date: Mon, 10 Apr 2023 15:49:21 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Cornelia Huck , virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org, shahafs@nvidia.com, Satananda Burla Message-ID: <20230410154518-mutt-send-email-mst@kernel.org> References: <20230330225834.506969-1-parav@nvidia.com> <20230330225834.506969-9-parav@nvidia.com> <20230404032922-mutt-send-email-mst@kernel.org> <87jzysjd4g.fsf@redhat.com> <20230404084126-mutt-send-email-mst@kernel.org> <878rf7kcna.fsf@redhat.com> <20230404102053-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-comment] Re: [PATCH 08/11] transport-pci: Introduce virtio extended capability On Mon, Apr 10, 2023 at 12:21:56PM -0400, Parav Pandit wrote: > > > On 4/4/2023 10:37 AM, Michael S. Tsirkin wrote: > > On Tue, Apr 04, 2023 at 03:19:53PM +0200, Cornelia Huck wrote: > > > > > > What does it "Co-developed-by" mean exactly that Signed-off-by > > > > > > does not? > > > > > > > > > > AIUI, "Co-developed-by:" is more akin to a second "Author:", i.e. to > > > > > give attribution. (Linux kernel rules actually state that any > > > > > "Co-developed-by:" must be followed by a "Signed-off-by:" for that > > > > > author, but we don't really do DCO here, the S-o-b is more of a > > > > > convention.) > > > > > > > > > > > > Actually, we might want to generally, to signify agreement to the IPR. > > > > How about adding this to our rules? But in this case Satananda Burla is > > > > a TC member so yes, no problem. > > > > > > Adding a s-o-b requirement is not a bad idea... do you want to propose > > > an update? > > > > OK how about the following: > > > > --------------- > > The process for forwarding comments from others: > > > > Generally, subscribing to the virtio comments mailing list > > requires agreement to the OASIS feedback license, at > > https://www.oasis-open.org/who/ipr/feedback_license.pdf > > > It is not straight forward for non virtio tc member to realize above > obligation. > It is worth to document it in the section [1]. > > [1] > https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback > > Something like, > > From: > If you're interested in following ongoing development and can't join the > committee, I recommend you subscribe to the virtio-comment and virtio-dev > lists. > > To: > If you're interested in following ongoing development and can't join the > committee, I recommend you subscribe to the virtio-comment and virtio-dev > lists. Your contribution to above mailing lists is licensed under the OASIS > feedback license agreement describe at [1]. yes. unfortunately oasis does not let us tweak this section. > > When forwarding (in modified or unmodified form) comments from others, please > > make sure the commenter has read and agreed to the > > feedback license. If this is the case, please include the following: > > > > License-consent: commenter's name > > > > where commenter's name is a valid > > name-addr as specified in RFC 5322, see > > https://datatracker.ietf.org/doc/html/rfc5322#section-3.4 > > > > If the comment is on behalf of an organization, please use the > > organization's email address. > > > > > > If forwarding a comment from a TC member, please instead get consent to > > the full Virtio TC IPR, and then, as before, include > > > > License-consent: commenter's name > > > License-consent tag do not capture the contribution by other virtio tc > member(s) in the generated comment. > > Signed-off-by captures it. > So both tags are needed depending on comment contribution type. Attribution is nice but Signed-off-by is not that. And fundamentally people go read the PDF where the Signed-off-by does not appear at all no one pokes at git history. Let's just do: Thanks-to: name if you want attribution. will be helpful to fill in the thanks section in the spec and does not mention signatures. > Rest above change looks good to me. > > > If you are reusing a comment that has already been posted to the > > TC mailing list, the above tags are not required. > > > > --------------- > > > > We could reuse Signed-off-by though I am a bit concerned whether > > people will assume it's a DCO thing which everyone copies. > > Thoughts? This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/