From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B8711364AE for ; Wed, 15 May 2024 10:30:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715769057; cv=none; b=pE7PdM9yV75odEbJph6Ju2ZVFp+JVaekaAPok9714kBXSxXL7H2cEH/cR2doolYJ8eGMW5ZpXdIK/goa+0RtTUUJ/McLAR4fzVxenc7Q5dpBFi9qVEnwvUoBlZP94g57lKflvGi59UxcIwxSXvqE7jUf+AUa/KC4pqw5mxvyhcw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715769057; c=relaxed/simple; bh=XdBInb3ujeFGbSF+v77Wb1MjcdRDfotlYCOWomIZnEM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: In-Reply-To:Content-Type:Content-Disposition; b=qDmzo0qyq+L2HFPjuFL8Q50LddYcHj2F6iSMgUAa4gI3+qr5O0uiyIumnG0z5+4ExMbVdIpIVdc8zz4rgp4+RGOxf2qyOCvLv3D3aURwh/ZjNahZpdv6N+u/TtAvd6tuSXnrGPeuC5YFw6dGDN9DvxvvGgSkrEjIOZxjTzmGaDo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=jMkyU1av; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="jMkyU1av" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1715769054; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=B5hhAOeyQ8WDPxXrZYQdpJDr0n9E/AJ3Xctgzs+zEUM=; b=jMkyU1avF7JzH+93LCB+/TzdRio/TlzbSpb2s/0amTwfP5BDr7sKfydjd/uoUW/0YeTDdW 0VTNj2FAquSkumPbr+XuG2YftGIA6NSjOzL6wDW/MDxGr77gDztMQfoN2VKhey5Ho7ti+H K4T629tfTNGtqGeQQD4QgBdk7Xy1/FU= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-382-2wsNkCXVMHW-F_o5ZtK2aA-1; Wed, 15 May 2024 06:30:52 -0400 X-MC-Unique: 2wsNkCXVMHW-F_o5ZtK2aA-1 Received: by mail-wm1-f72.google.com with SMTP id 5b1f17b1804b1-41dc9c831acso36109355e9.0 for ; Wed, 15 May 2024 03:30:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715769050; x=1716373850; 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=B5hhAOeyQ8WDPxXrZYQdpJDr0n9E/AJ3Xctgzs+zEUM=; b=iFlT1wXT1njWhT849zfdpHnzeSBt4wmWKkeIimvJLXZtBNdLr3UVyh2wjVSwTMqRIj PxIsh0Fldg1HQ/JPL+WvpP41cCpc11Ec462S16E52M9DyomZQM/FAnobjgAshhUg8453 kLuhlRX07QRCrzpUgMV/I8v5ng8J1aYHAGAo4QsR1D1vP/MqooP6mvUC06jvcGNbWhYl 1FsoEsjY5aJpYV4YIlpPZ18WMas3g5c/2m+QjVNqd/rlowRlGWTc/s4dGuTOtszSg0Ou LoD0VsHhTNdqgHj3P/YIddhuTQmPveNq8KqXjh06jm207c1SMZCLqYewPCkIrVLcLLNo 2Yaw== X-Forwarded-Encrypted: i=1; AJvYcCWoLBx9bKYeUszYJIv8NItXHKBdAa8u3UQAFKgTGhwqmZ18ExAsE6EQ9ZK9FHA3hPp5WrSgAby3oZ/WKX2/fbALJ3ABNHNg82wjFg== X-Gm-Message-State: AOJu0YwpR5kSgO1H64wN0O0CxDlgh5fddR/ESaWTwyBDxppcfawXwRZA 9R84sH+lpAya8gSAdK+LLMg71vusy5NsKna8xoYh1w4hBbB1tu/sv3KPZ61NA0WrxmcKMVAoWtS IFeQ8bgLncku2R+9lqOCRTHSyMs9v/POJJ2lC4Rrg8G7SfmPKgAEJR9/Gkua5x8C7MzY= X-Received: by 2002:a05:600c:4503:b0:41c:66:18c2 with SMTP id 5b1f17b1804b1-41fbc91f1admr173943195e9.4.1715769050349; Wed, 15 May 2024 03:30:50 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHD7qmuuTMRfqYVOcBR10ZRIEgMpD1ZNClKxCO/f+tKRFTfEMZRFsdaeK+cOqmbVTzO56guiw== X-Received: by 2002:a05:600c:4503:b0:41c:66:18c2 with SMTP id 5b1f17b1804b1-41fbc91f1admr173942905e9.4.1715769049702; Wed, 15 May 2024 03:30:49 -0700 (PDT) Received: from redhat.com ([2a02:14f:175:c01e:6df5:7e14:ad03:85bd]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-41fccee9326sm229440665e9.35.2024.05.15.03.30.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 May 2024 03:30:49 -0700 (PDT) Date: Wed, 15 May 2024 06:30:44 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: "virtio-comment@lists.linux.dev" , "virtio-dev@lists.linux.dev" Subject: Re: [PATCH v3] README.md: update mailing list info Message-ID: <20240515062910-mutt-send-email-mst@kernel.org> References: <8f5db33c96d685fcebca3579b05d09b64dd720d9.1715766697.git.mst@redhat.com> Precedence: bulk X-Mailing-List: virtio-dev@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: 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 On Wed, May 15, 2024 at 10:14:46AM +0000, Parav Pandit wrote: > > > From: Michael S. Tsirkin > > Sent: Wednesday, May 15, 2024 3:23 PM > > > > As approved by the TC, we are moving to a less formal way of discussing the > > specification, on the mailing lists provided by the Linux Foundation: > > > > https://groups.oasis-open.org/higherlogic/ws/public/ballot?id=3820 > > > > Update README.md, CONTRIBUTING.md and newdevice.tex accordingly. > > > > Use this opportunity to explain when and how to use each mailing list. > > > > Oh yes, and device numbers are reserved through virtio-comment not > > through virtio-dev. Correct that. > > > > Signed-off-by: Michael S. Tsirkin > > --- > > > > changes from v3: > > update CONTRIBUTING.md and newdevice.tex changes from v2: > > Use this opportunity to explain when and how to use each mailing list. > > > > CONTRIBUTING.md | 2 +- > > README.md | 80 ++++++++++++++++++++++++++++++++++++++++++- > > ------ > > newdevice.tex | 3 +- > > 3 files changed, 72 insertions(+), 13 deletions(-) > > > > diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index > > 1330a98..ee7318e 100644 > > --- a/CONTRIBUTING.md > > +++ b/CONTRIBUTING.md > > @@ -10,7 +10,7 @@ in the TC's technical activity is invited to > href="https://www.oasis-open.org (Member, Voting Member, Persistent > > Non-Voting Member; Chair, Secretary...)

> > > >

Persons who are not TC members are invited to open issues and provide > > comments using this repository's GitHub Issues tracking facility or using the - > > TC's comment > > list. All such content created in GitHub Issues and/or posted to the TC's > href="https://lists.oasis-open.org/archives/virtio-comment/">archived > > comment list is governed by the terms of the > href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS > > Feedback License.

> > +TC's comment > > +list. All such content created in GitHub Issues and/or posted to > > +the TC's archived > > +comment list is governed by the terms of the > +href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OAS > > +IS Feedback License.

> > > >

Use of Contributions. As with all OASIS Technical Committee > > assets (TC Wiki, TC > href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues > > Tracker, TC General > > Discussion List archives, TC OASIS > > Library assets), content placed into this GitHub repository is visible and > > publicly accessible. Subject to applicable licensing rules, the repository > > content may be re-used freely, including the creation and publication of > > derivative works.

> > > > diff --git a/README.md b/README.md > > index 2bdf485..c06caf6 100644 > > --- a/README.md > > +++ b/README.md > > @@ -76,11 +76,12 @@ font packages. > >
> > > >

Providing Feedback

> > -Feedback must be provided the virtio-comment mailing > > list, -and archived in the mailing list archives. > > -

See > -HREF="https://www.oasis- > > open.org/committees/tc_home.php?wg_abbrev=virtio#feedback"> > > -https://www.oasis- > > open.org/committees/tc_home.php?wg_abbrev=virtio#feedback > > +Informal feedback is accepted through the > > +virtio-comment mailing list, and is archived in > HREF="https://lore.kernel.org/virtio-comment/">the mailing list archives. > > +To provide feedback, subscribe by sending mail to > > +virtio-comment+ > > +subscribe@lists.linux.dev, then after confirming you agree to the > > +IPR sending your feedback to > > +virtio- > > comment@lists.linux.dev. > >

Note that only plain text part of the message is archived, and all > > attachments are stripped. Accordingly, messages sent to the mailing list > > should use text/plain encoding and not @@ -106,8 +107,38 @@ Signed-off- > > by: Name <email>
git format-patch -o proposal1/ HEAD~1..
... > > generates a new directory proposal1/ and a file starting with 0001- ...
> >

-git send-email --to=virtio-comment@lists.oasis-open.org > > proposal1/0001-* > > +git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-* > > > > + > > +

> > +
When to use the virtio-comment mailing list:
> > + questions and change proposals for the Virtio specification, > > + including the specification of basic functionality, transports and > > + devices. > > +
> > + > > +
When not to use the virtio-comment mailing list:
> > + questions and change proposals for Virtio drivers and devices > > + implementing the specification. > > + (please use the virtio-dev > > mailing list for this). > > +
> > + > > +
To do:
> > +
> > + send email preferably in text format (best for archiving). > > +
> > + > > +
Not to do:
> > +
> > +
    > > +
  • copy both virtio-dev and virtio-comment mailing lists (instead, > > +pick one);
  • send full copies of the virtio spec (in any format). > > +
> > +
> > + > > +
> >

Note for TC Members

> >

TC Members should review TC specific process rules under "Further > > Description of this Repository" > > @@ -116,16 +147,43 @@ HREF="https://github.com/oasis-tcs/virtio- > > admin">https://github.com/oasis-tcs/vi > > > > > >

Implementation discussion

> > -Implementation discussion should take place on the virtio- > > dev mailing list, -and be archived in the mailing list archives. > > -

See > -HREF="https://www.oasis- > > open.org/committees/tc_home.php?wg_abbrev=virtio#feedback"> > > -https://www.oasis- > > open.org/committees/tc_home.php?wg_abbrev=virtio#feedback > > +Implementation discussion takes place on the > > +virtio-dev mailing list, and is archived in > HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives. > > +To participate in the discussion, subscribe by sending mail to > > + > > +virtio-dev+subscribe@lists.linux.dev. > > +After agreeing to the IPR, to participate in the discussion, send mail > > +to virtio-dev@lists.linux.dev. > >

This is the correct list to copy on Linux virtio UAPI change proposals. > >

Note that only the plain text part of the message is archived, and all > > attachments are stripped. Accordingly, messages sent to the mailing list > > should use text/plain encoding and not have any attachments. > > + > > +

> > +
When to use the virtio-dev mailing list:
> > + questions and change proposals for Virtio drivers and devices > > + implementing the specification. > > +
> > + > > +
When not to use the virtio-dev mailing list:
> > + questions and change proposals for the Virtio specification, > > + including the specification of basic functionality, transports and > > + devices (please use the > > virtio-comment mailing list for this). > > +
> > +
To do:
> > +
> > + send email preferably in text format (best for archiving). > > +
> > + > > +
Not to do:
> > +
> > +copy both virtio-dev and virtio-comment mailing lists (instead, pick one). > > +
> > +
> > + > >

Use of github issues

> > Note: according to the virtio TC rules, all official TC communication is taking > > place on one of the TC mailing lists. > > diff --git a/newdevice.tex b/newdevice.tex index 28e1c7b..ed0124b 100644 > > --- a/newdevice.tex > > +++ b/newdevice.tex > > @@ -29,7 +29,8 @@ \section{What Device Configuration Space > > Layout?}\label{sec:Creating New Device \section{What Device > > Number?}\label{sec:Creating New Device Types / What Device Number?} > > > > Device numbers can be reserved by the OASIS committee: email -virtio- > > dev@lists.oasis-open.org to secure a unique one. > > +virtio-comment@lists.linux.dev (after subscribing through > > +virtio-comment+subscribe@lists.linux.dev) to secure a unique one. > > > > Meanwhile for experimental drivers, use 65535 and work backwards. > > > > -- > > MST > > > Reviewed-by: Parav Pandit > > I see that patches are posted on virtio-comment for balloon device. > Should community wait for this patch to be merged or ballot 3820 is good enough to consider this new mailing list active? I would wait until next Monday at least. Give everyone time to subscribe to the new list. -- MST