[PATCH v3] README.md: update mailing list info

[PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

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 <mst@redhat.com>
---

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 <a href="https://www.oasis-open.org
 (Member, Voting Member, Persistent Non-Voting Member; Chair, Secretary...)</p>
 
 <p>Persons who are not TC members are invited to open issues and provide comments using this repository's <a href="https://github.com/oasis-tcs/virtio-spec/issues/new">GitHub Issues</a> tracking facility or using the
-TC's <a href="https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio">comment list</a>.  All such content created in GitHub Issues and/or posted to the TC's <a href="https://lists.oasis-open.org/archives/virtio-comment/">archived comment list</a> is governed by the terms of the <a href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS Feedback License</a>.</p>
+TC's <a href="mailto:virtio-comment+subscribe@lists.linux.dev">comment list</a>.  All such content created in GitHub Issues and/or posted to the TC's <a href="https://lore.kernel.org/virtio-comment/">archived comment list</a> is governed by the terms of the <a href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS Feedback License</a>.</p>
 
 <p><b>Use of Contributions</b>.  As with all OASIS Technical Committee assets (TC <a href="https://wiki.oasis-open.org/">Wiki</a>, TC <a href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues Tracker</a>, TC <a href="https://lists.oasis-open.org/archives/">General Discussion List archives</a>, TC <a href="http://docs.oasis-open.org/">OASIS Library</a> assets), content placed into this GitHub repository is visible and publicly accessible.  Subject to applicable <a href="https://github.com/oasis-tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the repository content may be re-used freely, including the creation and publication of derivative works.</p>
 
diff --git a/README.md b/README.md
index 2bdf485..c06caf6 100644
--- a/README.md
+++ b/README.md
@@ -76,11 +76,12 @@ font packages.
 <dd>
 </dl>
 <h4>Providing Feedback</h4>
-Feedback must be provided the <strong>virtio-comment</strong> mailing list,
-and archived in the mailing list archives.
-<p>See <A
-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</A>
+Informal feedback is accepted through the <strong>virtio-comment</strong> mailing list,
+and is archived in <A HREF="https://lore.kernel.org/virtio-comment/">the mailing list archives</A>.
+To provide feedback, subscribe by sending mail to
+<HREF="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comment+subscribe@lists.linux.dev</A>,
+then after confirming you agree to the IPR sending your feedback to
+<HREF="mailto:virtio-comment@lists.linux.dev">virtio-comment@lists.linux.dev</A>.
 <p>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 &lt;email&gt;<br>
 git format-patch -o proposal1/ HEAD~1..<br>
 ... generates a new directory proposal1/ and a file starting with 0001- ...<br>
 <p>
-git send-email --to=virtio-comment@lists.oasis-open.org proposal1/0001-*
+git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
 </code>
+
+<dl>
+<dt>When to use the virtio-comment mailing list:</dt>
+<dd>
+  questions and change proposals for the Virtio specification,
+  including the specification of basic functionality, transports and
+  devices.
+</dd>
+
+<dt>When <em>not</em> to use the virtio-comment mailing list:</dt>
+<dd>
+  questions and change proposals for Virtio drivers and devices
+  implementing the specification.
+  (please use the <A HREF="mailto:virtio-dev@lists.linux.dev"> virtio-dev mailing list</A> for this).
+</dd>
+
+<dt>To do:</dt>
+<dd>
+ send email preferably in text format (best for archiving).
+</dd>
+
+<dt>Not to do:</dt>
+<dd>
+<ul>
+<li> copy both virtio-dev and virtio-comment mailing lists (instead, pick one);
+<li> send full copies of the virtio spec (in any format).
+</ul>
+</dd>
+
+</dl>
 <h4>Note for TC Members</h4>
 <p>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
 
 </div>
 <h4>Implementation discussion</h4>
-Implementation discussion should take place on the <strong>virtio-dev</strong> mailing list,
-and be archived in the mailing list archives.
-<p>See <A
-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</A>
+Implementation discussion takes place on the <strong>virtio-dev</strong> mailing list,
+and is archived in <A HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives</A>.
+To participate in the discussion, subscribe by sending mail to
+<HREF="mailto:virtio-dev+subscribe@lists.linux.dev">
+virtio-dev+subscribe@lists.linux.dev</A>.
+After agreeing to the IPR, to participate in the discussion, send
+mail to <HREF="mailto:virtio-dev@lists.linux.dev">virtio-dev@lists.linux.dev</A>.
 <p>This is the correct list to copy on Linux virtio UAPI change proposals.
 <p>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.
+
+<dl>
+<dt>When to use the virtio-dev mailing list:</dt>
+<dd>
+  questions and change proposals for Virtio drivers and devices
+  implementing the specification.
+</dd>
+
+<dt>When <em>not</em> to use the virtio-dev mailing list:</dt>
+<dd>
+  questions and change proposals for the Virtio specification,
+  including the specification of basic functionality, transports and
+  devices (please use the <A HREF="mailto:virtio-comment@lists.linux.dev"> virtio-comment mailing list</A> for this).
+</dd>
+<dt>To do:</dt>
+<dd>
+ send email preferably in text format (best for archiving).
+</dd>
+
+<dt>Not to do:</dt>
+<dd>
+copy both virtio-dev and virtio-comment mailing lists (instead, pick one).
+</dd>
+</dl>
+
 <h4>Use of github issues</h4>
 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

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> 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 <mst@redhat.com>
> ---
> 
> 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 <a
> href="https://www.oasis-open.org  (Member, Voting Member, Persistent
> Non-Voting Member; Chair, Secretary...)</p>
> 
>  <p>Persons who are not TC members are invited to open issues and provide
> comments using this repository's <a href="https://github.com/oasis-
> tcs/virtio-spec/issues/new">GitHub Issues</a> tracking facility or using the -
> TC's <a href="https://www.oasis-
> open.org/committees/comments/index.php?wg_abbrev=virtio">comment
> list</a>.  All such content created in GitHub Issues and/or posted to the TC's <a
> href="https://lists.oasis-open.org/archives/virtio-comment/">archived
> comment list</a> is governed by the terms of the <a
> href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS
> Feedback License</a>.</p>
> +TC's <a href="mailto:virtio-comment+subscribe@lists.linux.dev">comment
> +list</a>.  All such content created in GitHub Issues and/or posted to
> +the TC's <a href="https://lore.kernel.org/virtio-comment/">archived
> +comment list</a> is governed by the terms of the <a
> +href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OAS
> +IS Feedback License</a>.</p>
> 
>  <p><b>Use of Contributions</b>.  As with all OASIS Technical Committee
> assets (TC <a href="https://wiki.oasis-open.org/">Wiki</a>, TC <a
> href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues
> Tracker</a>, TC <a href="https://lists.oasis-open.org/archives/">General
> Discussion List archives</a>, TC <a href="http://docs.oasis-open.org/">OASIS
> Library</a> assets), content placed into this GitHub repository is visible and
> publicly accessible.  Subject to applicable <a href="https://github.com/oasis-
> tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the repository
> content may be re-used freely, including the creation and publication of
> derivative works.</p>
> 
> diff --git a/README.md b/README.md
> index 2bdf485..c06caf6 100644
> --- a/README.md
> +++ b/README.md
> @@ -76,11 +76,12 @@ font packages.
>  <dd>
>  </dl>
>  <h4>Providing Feedback</h4>
> -Feedback must be provided the <strong>virtio-comment</strong> mailing
> list, -and archived in the mailing list archives.
> -<p>See <A
> -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</A>
> +Informal feedback is accepted through the
> +<strong>virtio-comment</strong> mailing list, and is archived in <A
> HREF="https://lore.kernel.org/virtio-comment/">the mailing list archives</A>.
> +To provide feedback, subscribe by sending mail to
> +<HREF="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comment+
> +subscribe@lists.linux.dev</A>, then after confirming you agree to the
> +IPR sending your feedback to
> +<HREF="mailto:virtio-comment@lists.linux.dev">virtio-
> comment@lists.linux.dev</A>.
>  <p>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 &lt;email&gt;<br>  git format-patch -o proposal1/ HEAD~1..<br>  ...
> generates a new directory proposal1/ and a file starting with 0001- ...<br>
> <p> -git send-email --to=virtio-comment@lists.oasis-open.org
> proposal1/0001-*
> +git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
>  </code>
> +
> +<dl>
> +<dt>When to use the virtio-comment mailing list:</dt> <dd>
> +  questions and change proposals for the Virtio specification,
> +  including the specification of basic functionality, transports and
> +  devices.
> +</dd>
> +
> +<dt>When <em>not</em> to use the virtio-comment mailing list:</dt> <dd>
> +  questions and change proposals for Virtio drivers and devices
> +  implementing the specification.
> +  (please use the <A HREF="mailto:virtio-dev@lists.linux.dev"> virtio-dev
> mailing list</A> for this).
> +</dd>
> +
> +<dt>To do:</dt>
> +<dd>
> + send email preferably in text format (best for archiving).
> +</dd>
> +
> +<dt>Not to do:</dt>
> +<dd>
> +<ul>
> +<li> copy both virtio-dev and virtio-comment mailing lists (instead,
> +pick one); <li> send full copies of the virtio spec (in any format).
> +</ul>
> +</dd>
> +
> +</dl>
>  <h4>Note for TC Members</h4>
>  <p>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
> 
>  </div>
>  <h4>Implementation discussion</h4>
> -Implementation discussion should take place on the <strong>virtio-
> dev</strong> mailing list, -and be archived in the mailing list archives.
> -<p>See <A
> -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</A>
> +Implementation discussion takes place on the
> +<strong>virtio-dev</strong> mailing list, and is archived in <A
> HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives</A>.
> +To participate in the discussion, subscribe by sending mail to
> +<HREF="mailto:virtio-dev+subscribe@lists.linux.dev">
> +virtio-dev+subscribe@lists.linux.dev</A>.
> +After agreeing to the IPR, to participate in the discussion, send mail
> +to <HREF="mailto:virtio-dev@lists.linux.dev">virtio-dev@lists.linux.dev</A>.
>  <p>This is the correct list to copy on Linux virtio UAPI change proposals.
>  <p>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.
> +
> +<dl>
> +<dt>When to use the virtio-dev mailing list:</dt> <dd>
> +  questions and change proposals for Virtio drivers and devices
> +  implementing the specification.
> +</dd>
> +
> +<dt>When <em>not</em> to use the virtio-dev mailing list:</dt> <dd>
> +  questions and change proposals for the Virtio specification,
> +  including the specification of basic functionality, transports and
> +  devices (please use the <A HREF="mailto:virtio-comment@lists.linux.dev">
> virtio-comment mailing list</A> for this).
> +</dd>
> +<dt>To do:</dt>
> +<dd>
> + send email preferably in text format (best for archiving).
> +</dd>
> +
> +<dt>Not to do:</dt>
> +<dd>
> +copy both virtio-dev and virtio-comment mailing lists (instead, pick one).
> +</dd>
> +</dl>
> +
>  <h4>Use of github issues</h4>
>  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 <parav@nvidia.com>

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?

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Wed, May 15, 2024 at 10:14:46AM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > 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 <mst@redhat.com>
> > ---
> > 
> > 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 <a
> > href="https://www.oasis-open.org  (Member, Voting Member, Persistent
> > Non-Voting Member; Chair, Secretary...)</p>
> > 
> >  <p>Persons who are not TC members are invited to open issues and provide
> > comments using this repository's <a href="https://github.com/oasis-
> > tcs/virtio-spec/issues/new">GitHub Issues</a> tracking facility or using the -
> > TC's <a href="https://www.oasis-
> > open.org/committees/comments/index.php?wg_abbrev=virtio">comment
> > list</a>.  All such content created in GitHub Issues and/or posted to the TC's <a
> > href="https://lists.oasis-open.org/archives/virtio-comment/">archived
> > comment list</a> is governed by the terms of the <a
> > href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS
> > Feedback License</a>.</p>
> > +TC's <a href="mailto:virtio-comment+subscribe@lists.linux.dev">comment
> > +list</a>.  All such content created in GitHub Issues and/or posted to
> > +the TC's <a href="https://lore.kernel.org/virtio-comment/">archived
> > +comment list</a> is governed by the terms of the <a
> > +href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OAS
> > +IS Feedback License</a>.</p>
> > 
> >  <p><b>Use of Contributions</b>.  As with all OASIS Technical Committee
> > assets (TC <a href="https://wiki.oasis-open.org/">Wiki</a>, TC <a
> > href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues
> > Tracker</a>, TC <a href="https://lists.oasis-open.org/archives/">General
> > Discussion List archives</a>, TC <a href="http://docs.oasis-open.org/">OASIS
> > Library</a> assets), content placed into this GitHub repository is visible and
> > publicly accessible.  Subject to applicable <a href="https://github.com/oasis-
> > tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the repository
> > content may be re-used freely, including the creation and publication of
> > derivative works.</p>
> > 
> > diff --git a/README.md b/README.md
> > index 2bdf485..c06caf6 100644
> > --- a/README.md
> > +++ b/README.md
> > @@ -76,11 +76,12 @@ font packages.
> >  <dd>
> >  </dl>
> >  <h4>Providing Feedback</h4>
> > -Feedback must be provided the <strong>virtio-comment</strong> mailing
> > list, -and archived in the mailing list archives.
> > -<p>See <A
> > -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</A>
> > +Informal feedback is accepted through the
> > +<strong>virtio-comment</strong> mailing list, and is archived in <A
> > HREF="https://lore.kernel.org/virtio-comment/">the mailing list archives</A>.
> > +To provide feedback, subscribe by sending mail to
> > +<HREF="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comment+
> > +subscribe@lists.linux.dev</A>, then after confirming you agree to the
> > +IPR sending your feedback to
> > +<HREF="mailto:virtio-comment@lists.linux.dev">virtio-
> > comment@lists.linux.dev</A>.
> >  <p>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 &lt;email&gt;<br>  git format-patch -o proposal1/ HEAD~1..<br>  ...
> > generates a new directory proposal1/ and a file starting with 0001- ...<br>
> > <p> -git send-email --to=virtio-comment@lists.oasis-open.org
> > proposal1/0001-*
> > +git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
> >  </code>
> > +
> > +<dl>
> > +<dt>When to use the virtio-comment mailing list:</dt> <dd>
> > +  questions and change proposals for the Virtio specification,
> > +  including the specification of basic functionality, transports and
> > +  devices.
> > +</dd>
> > +
> > +<dt>When <em>not</em> to use the virtio-comment mailing list:</dt> <dd>
> > +  questions and change proposals for Virtio drivers and devices
> > +  implementing the specification.
> > +  (please use the <A HREF="mailto:virtio-dev@lists.linux.dev"> virtio-dev
> > mailing list</A> for this).
> > +</dd>
> > +
> > +<dt>To do:</dt>
> > +<dd>
> > + send email preferably in text format (best for archiving).
> > +</dd>
> > +
> > +<dt>Not to do:</dt>
> > +<dd>
> > +<ul>
> > +<li> copy both virtio-dev and virtio-comment mailing lists (instead,
> > +pick one); <li> send full copies of the virtio spec (in any format).
> > +</ul>
> > +</dd>
> > +
> > +</dl>
> >  <h4>Note for TC Members</h4>
> >  <p>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
> > 
> >  </div>
> >  <h4>Implementation discussion</h4>
> > -Implementation discussion should take place on the <strong>virtio-
> > dev</strong> mailing list, -and be archived in the mailing list archives.
> > -<p>See <A
> > -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</A>
> > +Implementation discussion takes place on the
> > +<strong>virtio-dev</strong> mailing list, and is archived in <A
> > HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives</A>.
> > +To participate in the discussion, subscribe by sending mail to
> > +<HREF="mailto:virtio-dev+subscribe@lists.linux.dev">
> > +virtio-dev+subscribe@lists.linux.dev</A>.
> > +After agreeing to the IPR, to participate in the discussion, send mail
> > +to <HREF="mailto:virtio-dev@lists.linux.dev">virtio-dev@lists.linux.dev</A>.
> >  <p>This is the correct list to copy on Linux virtio UAPI change proposals.
> >  <p>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.
> > +
> > +<dl>
> > +<dt>When to use the virtio-dev mailing list:</dt> <dd>
> > +  questions and change proposals for Virtio drivers and devices
> > +  implementing the specification.
> > +</dd>
> > +
> > +<dt>When <em>not</em> to use the virtio-dev mailing list:</dt> <dd>
> > +  questions and change proposals for the Virtio specification,
> > +  including the specification of basic functionality, transports and
> > +  devices (please use the <A HREF="mailto:virtio-comment@lists.linux.dev">
> > virtio-comment mailing list</A> for this).
> > +</dd>
> > +<dt>To do:</dt>
> > +<dd>
> > + send email preferably in text format (best for archiving).
> > +</dd>
> > +
> > +<dt>Not to do:</dt>
> > +<dd>
> > +copy both virtio-dev and virtio-comment mailing lists (instead, pick one).
> > +</dd>
> > +</dl>
> > +
> >  <h4>Use of github issues</h4>
> >  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 <parav@nvidia.com>
> 
> 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

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Wednesday, May 15, 2024 4:01 PM
> 
> On Wed, May 15, 2024 at 10:14:46AM +0000, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin <mst@redhat.com>
> > > 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 <mst@redhat.com>
> > > ---
> > >
> > > 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 <a
> > > href="https://www.oasis-open.org  (Member, Voting Member, Persistent
> > > Non-Voting Member; Chair, Secretary...)</p>
> > >
> > >  <p>Persons who are not TC members are invited to open issues and
> > > provide comments using this repository's <a
> > > href="https://github.com/oasis- tcs/virtio-spec/issues/new">GitHub
> > > Issues</a> tracking facility or using the - TC's <a
> > > href="https://www.oasis-
> > >
> open.org/committees/comments/index.php?wg_abbrev=virtio">comment
> > > list</a>.  All such content created in GitHub Issues and/or posted
> > > to the TC's <a
> > > href="https://lists.oasis-open.org/archives/virtio-comment/">archive
> > > d comment list</a> is governed by the terms of the <a
> > > href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">
> > > OASIS
> > > Feedback License</a>.</p>
> > > +TC's <a
> > > +href="mailto:virtio-comment+subscribe@lists.linux.dev">comment
> > > +list</a>.  All such content created in GitHub Issues and/or posted
> > > +to the TC's <a
> > > +href="https://lore.kernel.org/virtio-comment/">archived
> > > +comment list</a> is governed by the terms of the <a
> > > +href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa"
> > > +>OAS
> > > +IS Feedback License</a>.</p>
> > >
> > >  <p><b>Use of Contributions</b>.  As with all OASIS Technical
> > > Committee assets (TC <a
> > > href="https://wiki.oasis-open.org/">Wiki</a>, TC <a
> > > href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues
> > > Tracker</a>, TC <a
> > > href="https://lists.oasis-open.org/archives/">General
> > > Discussion List archives</a>, TC <a
> > > href="http://docs.oasis-open.org/">OASIS
> > > Library</a> assets), content placed into this GitHub repository is
> > > visible and publicly accessible.  Subject to applicable <a
> > > href="https://github.com/oasis-
> > > tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the
> > > repository content may be re-used freely, including the creation and
> > > publication of derivative works.</p>
> > >
> > > diff --git a/README.md b/README.md
> > > index 2bdf485..c06caf6 100644
> > > --- a/README.md
> > > +++ b/README.md
> > > @@ -76,11 +76,12 @@ font packages.
> > >  <dd>
> > >  </dl>
> > >  <h4>Providing Feedback</h4>
> > > -Feedback must be provided the <strong>virtio-comment</strong>
> > > mailing list, -and archived in the mailing list archives.
> > > -<p>See <A
> > > -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</A>
> > > +Informal feedback is accepted through the
> > > +<strong>virtio-comment</strong> mailing list, and is archived in <A
> > > HREF="https://lore.kernel.org/virtio-comment/">the mailing list
> archives</A>.
> > > +To provide feedback, subscribe by sending mail to
> > > +<HREF="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comm
> > > +ent+ subscribe@lists.linux.dev</A>, then after confirming you agree
> > > +to the IPR sending your feedback to
> > > +<HREF="mailto:virtio-comment@lists.linux.dev">virtio-
> > > comment@lists.linux.dev</A>.
> > >  <p>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 &lt;email&gt;<br>  git format-patch -o proposal1/ HEAD~1..<br>
> ...
> > > generates a new directory proposal1/ and a file starting with 0001-
> > > ...<br> <p> -git send-email --to=virtio-comment@lists.oasis-open.org
> > > proposal1/0001-*
> > > +git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
> > >  </code>
> > > +
> > > +<dl>
> > > +<dt>When to use the virtio-comment mailing list:</dt> <dd>
> > > +  questions and change proposals for the Virtio specification,
> > > +  including the specification of basic functionality, transports
> > > +and
> > > +  devices.
> > > +</dd>
> > > +
> > > +<dt>When <em>not</em> to use the virtio-comment mailing list:</dt>
> > > +<dd>
> > > +  questions and change proposals for Virtio drivers and devices
> > > +  implementing the specification.
> > > +  (please use the <A HREF="mailto:virtio-dev@lists.linux.dev">
> > > +virtio-dev
> > > mailing list</A> for this).
> > > +</dd>
> > > +
> > > +<dt>To do:</dt>
> > > +<dd>
> > > + send email preferably in text format (best for archiving).
> > > +</dd>
> > > +
> > > +<dt>Not to do:</dt>
> > > +<dd>
> > > +<ul>
> > > +<li> copy both virtio-dev and virtio-comment mailing lists
> > > +(instead, pick one); <li> send full copies of the virtio spec (in any format).
> > > +</ul>
> > > +</dd>
> > > +
> > > +</dl>
> > >  <h4>Note for TC Members</h4>
> > >  <p>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
> > >
> > >  </div>
> > >  <h4>Implementation discussion</h4>
> > > -Implementation discussion should take place on the <strong>virtio-
> > > dev</strong> mailing list, -and be archived in the mailing list archives.
> > > -<p>See <A
> > > -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</A>
> > > +Implementation discussion takes place on the
> > > +<strong>virtio-dev</strong> mailing list, and is archived in <A
> > > HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives</A>.
> > > +To participate in the discussion, subscribe by sending mail to
> > > +<HREF="mailto:virtio-dev+subscribe@lists.linux.dev">
> > > +virtio-dev+subscribe@lists.linux.dev</A>.
> > > +After agreeing to the IPR, to participate in the discussion, send
> > > +mail to <HREF="mailto:virtio-dev@lists.linux.dev">virtio-
> dev@lists.linux.dev</A>.
> > >  <p>This is the correct list to copy on Linux virtio UAPI change proposals.
> > >  <p>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.
> > > +
> > > +<dl>
> > > +<dt>When to use the virtio-dev mailing list:</dt> <dd>
> > > +  questions and change proposals for Virtio drivers and devices
> > > +  implementing the specification.
> > > +</dd>
> > > +
> > > +<dt>When <em>not</em> to use the virtio-dev mailing list:</dt> <dd>
> > > +  questions and change proposals for the Virtio specification,
> > > +  including the specification of basic functionality, transports
> > > +and
> > > +  devices (please use the <A
> > > +HREF="mailto:virtio-comment@lists.linux.dev">
> > > virtio-comment mailing list</A> for this).
> > > +</dd>
> > > +<dt>To do:</dt>
> > > +<dd>
> > > + send email preferably in text format (best for archiving).
> > > +</dd>
> > > +
> > > +<dt>Not to do:</dt>
> > > +<dd>
> > > +copy both virtio-dev and virtio-comment mailing lists (instead, pick one).
> > > +</dd>
> > > +</dl>
> > > +
> > >  <h4>Use of github issues</h4>
> > >  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 <parav@nvidia.com>
> >
> > 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.
Yes, make sense to me. I assume you would merge this patch before that? or this also needs a vote?

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Wed, May 15, 2024 at 10:32:53AM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, May 15, 2024 4:01 PM
> > 
> > On Wed, May 15, 2024 at 10:14:46AM +0000, Parav Pandit wrote:
> > >
> > > > From: Michael S. Tsirkin <mst@redhat.com>
> > > > 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 <mst@redhat.com>
> > > > ---
> > > >
> > > > 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 <a
> > > > href="https://www.oasis-open.org  (Member, Voting Member, Persistent
> > > > Non-Voting Member; Chair, Secretary...)</p>
> > > >
> > > >  <p>Persons who are not TC members are invited to open issues and
> > > > provide comments using this repository's <a
> > > > href="https://github.com/oasis- tcs/virtio-spec/issues/new">GitHub
> > > > Issues</a> tracking facility or using the - TC's <a
> > > > href="https://www.oasis-
> > > >
> > open.org/committees/comments/index.php?wg_abbrev=virtio">comment
> > > > list</a>.  All such content created in GitHub Issues and/or posted
> > > > to the TC's <a
> > > > href="https://lists.oasis-open.org/archives/virtio-comment/">archive
> > > > d comment list</a> is governed by the terms of the <a
> > > > href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">
> > > > OASIS
> > > > Feedback License</a>.</p>
> > > > +TC's <a
> > > > +href="mailto:virtio-comment+subscribe@lists.linux.dev">comment
> > > > +list</a>.  All such content created in GitHub Issues and/or posted
> > > > +to the TC's <a
> > > > +href="https://lore.kernel.org/virtio-comment/">archived
> > > > +comment list</a> is governed by the terms of the <a
> > > > +href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa"
> > > > +>OAS
> > > > +IS Feedback License</a>.</p>
> > > >
> > > >  <p><b>Use of Contributions</b>.  As with all OASIS Technical
> > > > Committee assets (TC <a
> > > > href="https://wiki.oasis-open.org/">Wiki</a>, TC <a
> > > > href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues
> > > > Tracker</a>, TC <a
> > > > href="https://lists.oasis-open.org/archives/">General
> > > > Discussion List archives</a>, TC <a
> > > > href="http://docs.oasis-open.org/">OASIS
> > > > Library</a> assets), content placed into this GitHub repository is
> > > > visible and publicly accessible.  Subject to applicable <a
> > > > href="https://github.com/oasis-
> > > > tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the
> > > > repository content may be re-used freely, including the creation and
> > > > publication of derivative works.</p>
> > > >
> > > > diff --git a/README.md b/README.md
> > > > index 2bdf485..c06caf6 100644
> > > > --- a/README.md
> > > > +++ b/README.md
> > > > @@ -76,11 +76,12 @@ font packages.
> > > >  <dd>
> > > >  </dl>
> > > >  <h4>Providing Feedback</h4>
> > > > -Feedback must be provided the <strong>virtio-comment</strong>
> > > > mailing list, -and archived in the mailing list archives.
> > > > -<p>See <A
> > > > -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</A>
> > > > +Informal feedback is accepted through the
> > > > +<strong>virtio-comment</strong> mailing list, and is archived in <A
> > > > HREF="https://lore.kernel.org/virtio-comment/">the mailing list
> > archives</A>.
> > > > +To provide feedback, subscribe by sending mail to
> > > > +<HREF="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comm
> > > > +ent+ subscribe@lists.linux.dev</A>, then after confirming you agree
> > > > +to the IPR sending your feedback to
> > > > +<HREF="mailto:virtio-comment@lists.linux.dev">virtio-
> > > > comment@lists.linux.dev</A>.
> > > >  <p>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 &lt;email&gt;<br>  git format-patch -o proposal1/ HEAD~1..<br>
> > ...
> > > > generates a new directory proposal1/ and a file starting with 0001-
> > > > ...<br> <p> -git send-email --to=virtio-comment@lists.oasis-open.org
> > > > proposal1/0001-*
> > > > +git send-email --to=virtio-comment@lists.linux.dev proposal1/0001-*
> > > >  </code>
> > > > +
> > > > +<dl>
> > > > +<dt>When to use the virtio-comment mailing list:</dt> <dd>
> > > > +  questions and change proposals for the Virtio specification,
> > > > +  including the specification of basic functionality, transports
> > > > +and
> > > > +  devices.
> > > > +</dd>
> > > > +
> > > > +<dt>When <em>not</em> to use the virtio-comment mailing list:</dt>
> > > > +<dd>
> > > > +  questions and change proposals for Virtio drivers and devices
> > > > +  implementing the specification.
> > > > +  (please use the <A HREF="mailto:virtio-dev@lists.linux.dev">
> > > > +virtio-dev
> > > > mailing list</A> for this).
> > > > +</dd>
> > > > +
> > > > +<dt>To do:</dt>
> > > > +<dd>
> > > > + send email preferably in text format (best for archiving).
> > > > +</dd>
> > > > +
> > > > +<dt>Not to do:</dt>
> > > > +<dd>
> > > > +<ul>
> > > > +<li> copy both virtio-dev and virtio-comment mailing lists
> > > > +(instead, pick one); <li> send full copies of the virtio spec (in any format).
> > > > +</ul>
> > > > +</dd>
> > > > +
> > > > +</dl>
> > > >  <h4>Note for TC Members</h4>
> > > >  <p>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
> > > >
> > > >  </div>
> > > >  <h4>Implementation discussion</h4>
> > > > -Implementation discussion should take place on the <strong>virtio-
> > > > dev</strong> mailing list, -and be archived in the mailing list archives.
> > > > -<p>See <A
> > > > -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</A>
> > > > +Implementation discussion takes place on the
> > > > +<strong>virtio-dev</strong> mailing list, and is archived in <A
> > > > HREF="https://lore.kernel.org/virtio-dev/">the mailing list archives</A>.
> > > > +To participate in the discussion, subscribe by sending mail to
> > > > +<HREF="mailto:virtio-dev+subscribe@lists.linux.dev">
> > > > +virtio-dev+subscribe@lists.linux.dev</A>.
> > > > +After agreeing to the IPR, to participate in the discussion, send
> > > > +mail to <HREF="mailto:virtio-dev@lists.linux.dev">virtio-
> > dev@lists.linux.dev</A>.
> > > >  <p>This is the correct list to copy on Linux virtio UAPI change proposals.
> > > >  <p>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.
> > > > +
> > > > +<dl>
> > > > +<dt>When to use the virtio-dev mailing list:</dt> <dd>
> > > > +  questions and change proposals for Virtio drivers and devices
> > > > +  implementing the specification.
> > > > +</dd>
> > > > +
> > > > +<dt>When <em>not</em> to use the virtio-dev mailing list:</dt> <dd>
> > > > +  questions and change proposals for the Virtio specification,
> > > > +  including the specification of basic functionality, transports
> > > > +and
> > > > +  devices (please use the <A
> > > > +HREF="mailto:virtio-comment@lists.linux.dev">
> > > > virtio-comment mailing list</A> for this).
> > > > +</dd>
> > > > +<dt>To do:</dt>
> > > > +<dd>
> > > > + send email preferably in text format (best for archiving).
> > > > +</dd>
> > > > +
> > > > +<dt>Not to do:</dt>
> > > > +<dd>
> > > > +copy both virtio-dev and virtio-comment mailing lists (instead, pick one).
> > > > +</dd>
> > > > +</dl>
> > > > +
> > > >  <h4>Use of github issues</h4>
> > > >  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 <parav@nvidia.com>
> > >
> > > 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.
> Yes, make sense to me. I assume you would merge this patch before
> that? or this also needs a vote?

Ideally a vote ... but I'm still working on fixing the voting system.
Let's see if I finish this work today.

-- 
MST

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

Hi Michael,

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Wednesday, May 15, 2024 4:07 PM

> > > I would wait until next Monday at least. Give everyone time to
> > > subscribe to the new list.

Can you please merge this patch?

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> Hi Michael,
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, May 15, 2024 4:07 PM
> 
> > > > I would wait until next Monday at least. Give everyone time to
> > > > subscribe to the new list.
> 
> Can you please merge this patch?

Pushed now.

-- 
MST

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, May 21, 2024 12:55 PM
> 
> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > Hi Michael,
> >
> > > From: Michael S. Tsirkin <mst@redhat.com>
> > > Sent: Wednesday, May 15, 2024 4:07 PM
> >
> > > > > I would wait until next Monday at least. Give everyone time to
> > > > > subscribe to the new list.
> >
> > Can you please merge this patch?
> 
> Pushed now.

Thanks Michael.
Cornelia mentioned in [1] that master and 1.4 should be merged.
1.4 is 17 patches behind the master including this one.
And 12 commits behind..

Can you please merge them? Without it, there are conflicts in patches.

Also, we need to update in the README.md on which branch to use for sending the patches.

[1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Tue, May 21, 2024 at 07:59:03AM +0000, Parav Pandit wrote:
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, May 21, 2024 12:55 PM
> > 
> > On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > > Hi Michael,
> > >
> > > > From: Michael S. Tsirkin <mst@redhat.com>
> > > > Sent: Wednesday, May 15, 2024 4:07 PM
> > >
> > > > > > I would wait until next Monday at least. Give everyone time to
> > > > > > subscribe to the new list.
> > >
> > > Can you please merge this patch?
> > 
> > Pushed now.
> 
> Thanks Michael.
> Cornelia mentioned in [1] that master and 1.4 should be merged.
> 1.4 is 17 patches behind the master including this one.
>
> And 12 commits behind..
> 
> Can you please merge them? Without it, there are conflicts in patches.
> 
> Also, we need to update in the README.md on which branch to use for sending the patches.
> 
> [1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

I think I'll let Cornelia do it. This patch should be cherry picked for
1.3 I think.

-- 
MST

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, May 21, 2024 1:34 PM
> 
> On Tue, May 21, 2024 at 07:59:03AM +0000, Parav Pandit wrote:
> >
> > > From: Michael S. Tsirkin <mst@redhat.com>
> > > Sent: Tuesday, May 21, 2024 12:55 PM
> > >
> > > On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > > > Hi Michael,
> > > >
> > > > > From: Michael S. Tsirkin <mst@redhat.com>
> > > > > Sent: Wednesday, May 15, 2024 4:07 PM
> > > >
> > > > > > > I would wait until next Monday at least. Give everyone time
> > > > > > > to subscribe to the new list.
> > > >
> > > > Can you please merge this patch?
> > >
> > > Pushed now.
> >
> > Thanks Michael.
> > Cornelia mentioned in [1] that master and 1.4 should be merged.
> > 1.4 is 17 patches behind the master including this one.
> >
> > And 12 commits behind..
> >
> > Can you please merge them? Without it, there are conflicts in patches.
> >
> > Also, we need to update in the README.md on which branch to use for
> sending the patches.
> >
> > [1]
> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.h
> > tml
> 
> I think I'll let Cornelia do it. This patch should be cherry picked for
> 1.3 I think.
Do you mean to cherry pick for 1.4 because 1.3 is already released?

RE: [PATCH v3] README.md: update mailing list info

[Cornelia Huck]

On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:

>> From: Michael S. Tsirkin <mst@redhat.com>
>> Sent: Tuesday, May 21, 2024 12:55 PM
>> 
>> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
>> > Hi Michael,
>> >
>> > > From: Michael S. Tsirkin <mst@redhat.com>
>> > > Sent: Wednesday, May 15, 2024 4:07 PM
>> >
>> > > > > I would wait until next Monday at least. Give everyone time to
>> > > > > subscribe to the new list.
>> >
>> > Can you please merge this patch?
>> 
>> Pushed now.
>
> Thanks Michael.
> Cornelia mentioned in [1] that master and 1.4 should be merged.
> 1.4 is 17 patches behind the master including this one.
> And 12 commits behind..
>
> Can you please merge them? Without it, there are conflicts in patches.
>
> Also, we need to update in the README.md on which branch to use for sending the patches.
>
> [1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

Repo status is a mess, because the state of the TC is currently a
mess...

* Before we can merge the branches, we need to do a proper Special
  Majority Vote to release 1.3 (which had been delayed since *last year*
  due to first the threatening migration, and then the actual
  troublesome migration.)
* The platform is still not working properly. For starters, we now know
  that other people besides myself are not getting any mail from the
  main TC list; given that the ballot approving use of the new lists has
  not gotten a vote from several usually reliable voters, I fear that
  mail delivery regarding ballots is broken for some people as well...

Before requesting a Special Majority Vote, IMNSHO we need to be sure
that voters actually get notified about it. [We have raised the issues
with mail delivery with OASIS staff, but I'm really unsure about the
current status.]

virtio-comment subscribers who are TC members as well: if you didn't get
any emails from either the main TC mailing list (you can check the
archives) or from the voting platform, we'd like to hear about it.

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Tuesday, May 21, 2024 3:29 PM
> 
> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> 
> >> From: Michael S. Tsirkin <mst@redhat.com>
> >> Sent: Tuesday, May 21, 2024 12:55 PM
> >>
> >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> >> > Hi Michael,
> >> >
> >> > > From: Michael S. Tsirkin <mst@redhat.com>
> >> > > Sent: Wednesday, May 15, 2024 4:07 PM
> >> >
> >> > > > > I would wait until next Monday at least. Give everyone time
> >> > > > > to subscribe to the new list.
> >> >
> >> > Can you please merge this patch?
> >>
> >> Pushed now.
> >
> > Thanks Michael.
> > Cornelia mentioned in [1] that master and 1.4 should be merged.
> > 1.4 is 17 patches behind the master including this one.
> > And 12 commits behind..
> >
> > Can you please merge them? Without it, there are conflicts in patches.
> >
> > Also, we need to update in the README.md on which branch to use for
> sending the patches.
> >
> > [1]
> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.h
> > tml
> 
> Repo status is a mess, because the state of the TC is currently a mess...
> 
> * Before we can merge the branches, we need to do a proper Special
>   Majority Vote to release 1.3 (which had been delayed since *last year*
>   due to first the threatening migration, and then the actual
>   troublesome migration.)
> * The platform is still not working properly. For starters, we now know
>   that other people besides myself are not getting any mail from the
>   main TC list; 
Can you please follow up with OASIS?

> given that the ballot approving use of the new lists has
>   not gotten a vote from several usually reliable voters, I fear that
>   mail delivery regarding ballots is broken for some people as well...
> 
I have followed up with OASIS for several of the members to fix their voting and other broken access rights.
Are you following up for the rest, or should I? Please let me know.

To my knowledge, voting is broken for Enrico Granata based on the ballot #03820 and previous ballot #184, #189 etc.
Which other reliable voters are we missing?

> Before requesting a Special Majority Vote, IMNSHO we need to be sure that
> voters actually get notified about it. [We have raised the issues with mail
> delivery with OASIS staff, but I'm really unsure about the current status.]
> 
Can you please check the current status with OASIS?
The migration by them is completed in March more than 2 months ago.

> virtio-comment subscribers who are TC members as well: if you didn't get any
> emails from either the main TC mailing list (you can check the
> archives) or from the voting platform, we'd like to hear about it.

Contributors are not blocked anymore as the reviews have started already with new list, which is good.
Your previous recommendation of using the branch 1.4 for all the spec patches, likely still stays the same. Right?

[1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Tue, May 21, 2024 at 12:02:13PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Tuesday, May 21, 2024 3:29 PM
> > 
> > On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> > 
> > >> From: Michael S. Tsirkin <mst@redhat.com>
> > >> Sent: Tuesday, May 21, 2024 12:55 PM
> > >>
> > >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > >> > Hi Michael,
> > >> >
> > >> > > From: Michael S. Tsirkin <mst@redhat.com>
> > >> > > Sent: Wednesday, May 15, 2024 4:07 PM
> > >> >
> > >> > > > > I would wait until next Monday at least. Give everyone time
> > >> > > > > to subscribe to the new list.
> > >> >
> > >> > Can you please merge this patch?
> > >>
> > >> Pushed now.
> > >
> > > Thanks Michael.
> > > Cornelia mentioned in [1] that master and 1.4 should be merged.
> > > 1.4 is 17 patches behind the master including this one.
> > > And 12 commits behind..
> > >
> > > Can you please merge them? Without it, there are conflicts in patches.
> > >
> > > Also, we need to update in the README.md on which branch to use for
> > sending the patches.
> > >
> > > [1]
> > > https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.h
> > > tml
> > 
> > Repo status is a mess, because the state of the TC is currently a mess...
> > 
> > * Before we can merge the branches, we need to do a proper Special
> >   Majority Vote to release 1.3 (which had been delayed since *last year*
> >   due to first the threatening migration, and then the actual
> >   troublesome migration.)
> > * The platform is still not working properly. For starters, we now know
> >   that other people besides myself are not getting any mail from the
> >   main TC list; 
> Can you please follow up with OASIS?
>
> > given that the ballot approving use of the new lists has
> >   not gotten a vote from several usually reliable voters, I fear that
> >   mail delivery regarding ballots is broken for some people as well...
> > 
> I have followed up with OASIS for several of the members to fix their voting and other broken access rights.
> Are you following up for the rest, or should I? Please let me know.
> 
> To my knowledge, voting is broken for Enrico Granata based on the ballot #03820 and previous ballot #184, #189 etc.
> Which other reliable voters are we missing?
> 
> > Before requesting a Special Majority Vote, IMNSHO we need to be sure that
> > voters actually get notified about it. [We have raised the issues with mail
> > delivery with OASIS staff, but I'm really unsure about the current status.]

voters actually get notified directly.

> Can you please check the current status with OASIS?
> The migration by them is completed in March more than 2 months ago.
> 
> > virtio-comment subscribers who are TC members as well: if you didn't get any
> > emails from either the main TC mailing list (you can check the
> > archives) or from the voting platform, we'd like to hear about it.
> 
> Contributors are not blocked anymore as the reviews have started already with new list, which is good.
> Your previous recommendation of using the branch 1.4 for all the spec patches, likely still stays the same. Right?
> 
> [1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

RE: [PATCH v3] README.md: update mailing list info

[Cornelia Huck]

On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:

>> From: Cornelia Huck <cohuck@redhat.com>
>> Sent: Tuesday, May 21, 2024 3:29 PM
>> 
>> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
>> 
>> >> From: Michael S. Tsirkin <mst@redhat.com>
>> >> Sent: Tuesday, May 21, 2024 12:55 PM
>> >>
>> >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
>> >> > Hi Michael,
>> >> >
>> >> > > From: Michael S. Tsirkin <mst@redhat.com>
>> >> > > Sent: Wednesday, May 15, 2024 4:07 PM
>> >> >
>> >> > > > > I would wait until next Monday at least. Give everyone time
>> >> > > > > to subscribe to the new list.
>> >> >
>> >> > Can you please merge this patch?
>> >>
>> >> Pushed now.
>> >
>> > Thanks Michael.
>> > Cornelia mentioned in [1] that master and 1.4 should be merged.
>> > 1.4 is 17 patches behind the master including this one.
>> > And 12 commits behind..
>> >
>> > Can you please merge them? Without it, there are conflicts in patches.
>> >
>> > Also, we need to update in the README.md on which branch to use for
>> sending the patches.
>> >
>> > [1]
>> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.h
>> > tml
>> 
>> Repo status is a mess, because the state of the TC is currently a mess...
>> 
>> * Before we can merge the branches, we need to do a proper Special
>>   Majority Vote to release 1.3 (which had been delayed since *last year*
>>   due to first the threatening migration, and then the actual
>>   troublesome migration.)
>> * The platform is still not working properly. For starters, we now know
>>   that other people besides myself are not getting any mail from the
>>   main TC list; 
> Can you please follow up with OASIS?

Well, it's not like we've been sitting idle and not been following up...

>
>> given that the ballot approving use of the new lists has
>>   not gotten a vote from several usually reliable voters, I fear that
>>   mail delivery regarding ballots is broken for some people as well...
>> 
> I have followed up with OASIS for several of the members to fix their voting and other broken access rights.
> Are you following up for the rest, or should I? Please let me know.

People have to tell me for me to do anything. If voting is not working,
please let the chairs know. I don't want to start another ballot if some
people are unable to participate.

>
> To my knowledge, voting is broken for Enrico Granata based on the ballot #03820 and previous ballot #184, #189 etc.
> Which other reliable voters are we missing?
>
>> Before requesting a Special Majority Vote, IMNSHO we need to be sure that
>> voters actually get notified about it. [We have raised the issues with mail
>> delivery with OASIS staff, but I'm really unsure about the current status.]
>> 
> Can you please check the current status with OASIS?
> The migration by them is completed in March more than 2 months ago.

The migration is "finished", problems persist, OASIS has been notified
multiple times. I, as a chair, do not consider myself fully
operational. The joys of outsourcing.

>
>> virtio-comment subscribers who are TC members as well: if you didn't get any
>> emails from either the main TC mailing list (you can check the
>> archives) or from the voting platform, we'd like to hear about it.
>
> Contributors are not blocked anymore as the reviews have started already with new list, which is good.
> Your previous recommendation of using the branch 1.4 for all the spec patches, likely still stays the same. Right?
>
> [1] https://lists.oasis-open.org/archives/virtio-comment/202401/msg00087.html

Yes, as long as we have not finalized 1.3, patches need to target
1.4. Yes, it's a mess, and I'm highly frustrated.

RE: [PATCH v3] README.md: update mailing list info

[Parav Pandit]

> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Tuesday, May 21, 2024 6:13 PM
> 
> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> 
> >> From: Cornelia Huck <cohuck@redhat.com>
> >> Sent: Tuesday, May 21, 2024 3:29 PM
> >>
> >> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> >>
> >> >> From: Michael S. Tsirkin <mst@redhat.com>
> >> >> Sent: Tuesday, May 21, 2024 12:55 PM
> >> >>
> >> >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> >> >> > Hi Michael,
> >> >> >
> >> >> > > From: Michael S. Tsirkin <mst@redhat.com>
> >> >> > > Sent: Wednesday, May 15, 2024 4:07 PM
> >> >> >
> >> >> > > > > I would wait until next Monday at least. Give everyone
> >> >> > > > > time to subscribe to the new list.
> >> >> >
> >> >> > Can you please merge this patch?
> >> >>
> >> >> Pushed now.
> >> >
> >> > Thanks Michael.
> >> > Cornelia mentioned in [1] that master and 1.4 should be merged.
> >> > 1.4 is 17 patches behind the master including this one.
> >> > And 12 commits behind..
> >> >
> >> > Can you please merge them? Without it, there are conflicts in patches.
> >> >
> >> > Also, we need to update in the README.md on which branch to use for
> >> sending the patches.
> >> >
> >> > [1]
> >> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg0008
> >> > 7.h
> >> > tml
> >>
> >> Repo status is a mess, because the state of the TC is currently a mess...
> >>
> >> * Before we can merge the branches, we need to do a proper Special
> >>   Majority Vote to release 1.3 (which had been delayed since *last year*
> >>   due to first the threatening migration, and then the actual
> >>   troublesome migration.)
> >> * The platform is still not working properly. For starters, we now know
> >>   that other people besides myself are not getting any mail from the
> >>   main TC list;
> > Can you please follow up with OASIS?
> 
> Well, it's not like we've been sitting idle and not been following up...
> 
Sure. Not sure why I sounded that way. I am sorry about it.
You mentioned you didn't know current status; this is why I asked if you can check the current status.
I see your voted for #03820, so I assumed that you got the email. :)

> >
> >> given that the ballot approving use of the new lists has
> >>   not gotten a vote from several usually reliable voters, I fear that
> >>   mail delivery regarding ballots is broken for some people as well...
> >>
> > I have followed up with OASIS for several of the members to fix their voting
> and other broken access rights.
> > Are you following up for the rest, or should I? Please let me know.
> 
> People have to tell me for me to do anything. If voting is not working,
> please let the chairs know. I don't want to start another ballot if some
> people are unable to participate.
> 
So it is working for 17 out of 19 voters as they voted in the latest ballot.
If the person does not get any emails from OASIS main list, it is likely doesn't get the ballot email too.
And they wouldn't know that they were supposed to vote, until someone tells them.

This is why I asked if you want to follow up.
I followed up with many to get their login etc sorted out.

> >
> > To my knowledge, voting is broken for Enrico Granata based on the ballot
> #03820 and previous ballot #184, #189 etc.
> > Which other reliable voters are we missing?
> >
> >> Before requesting a Special Majority Vote, IMNSHO we need to be sure that
> >> voters actually get notified about it. [We have raised the issues with mail
> >> delivery with OASIS staff, but I'm really unsure about the current status.]
> >>
> > Can you please check the current status with OASIS?
> > The migration by them is completed in March more than 2 months ago.
> 
> The migration is "finished", problems persist, OASIS has been notified
> multiple times. I, as a chair, do not consider myself fully
> operational. The joys of outsourcing.
> 
What are the missing things for you to be operational, maybe I can follow up on your behalf with OASIS?
If that reduces your load...

> >
> >> virtio-comment subscribers who are TC members as well: if you didn't get
> any
> >> emails from either the main TC mailing list (you can check the
> >> archives) or from the voting platform, we'd like to hear about it.
> >
> > Contributors are not blocked anymore as the reviews have started already
> with new list, which is good.
> > Your previous recommendation of using the branch 1.4 for all the spec
> patches, likely still stays the same. Right?
> >
> > [1] https://lists.oasis-open.org/archives/virtio-
> comment/202401/msg00087.html
> 
> Yes, as long as we have not finalized 1.3, patches need to target
> 1.4. Yes, it's a mess, and I'm highly frustrated.

Ok. got it. Thanks for the quick confirmation.

Re: [PATCH v3] README.md: update mailing list info

[Michael S. Tsirkin]

On Tue, May 21, 2024 at 01:24:25PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Tuesday, May 21, 2024 6:13 PM
> > 
> > On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> > 
> > >> From: Cornelia Huck <cohuck@redhat.com>
> > >> Sent: Tuesday, May 21, 2024 3:29 PM
> > >>
> > >> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> > >>
> > >> >> From: Michael S. Tsirkin <mst@redhat.com>
> > >> >> Sent: Tuesday, May 21, 2024 12:55 PM
> > >> >>
> > >> >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > >> >> > Hi Michael,
> > >> >> >
> > >> >> > > From: Michael S. Tsirkin <mst@redhat.com>
> > >> >> > > Sent: Wednesday, May 15, 2024 4:07 PM
> > >> >> >
> > >> >> > > > > I would wait until next Monday at least. Give everyone
> > >> >> > > > > time to subscribe to the new list.
> > >> >> >
> > >> >> > Can you please merge this patch?
> > >> >>
> > >> >> Pushed now.
> > >> >
> > >> > Thanks Michael.
> > >> > Cornelia mentioned in [1] that master and 1.4 should be merged.
> > >> > 1.4 is 17 patches behind the master including this one.
> > >> > And 12 commits behind..
> > >> >
> > >> > Can you please merge them? Without it, there are conflicts in patches.
> > >> >
> > >> > Also, we need to update in the README.md on which branch to use for
> > >> sending the patches.
> > >> >
> > >> > [1]
> > >> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg0008
> > >> > 7.h
> > >> > tml
> > >>
> > >> Repo status is a mess, because the state of the TC is currently a mess...
> > >>
> > >> * Before we can merge the branches, we need to do a proper Special
> > >>   Majority Vote to release 1.3 (which had been delayed since *last year*
> > >>   due to first the threatening migration, and then the actual
> > >>   troublesome migration.)
> > >> * The platform is still not working properly. For starters, we now know
> > >>   that other people besides myself are not getting any mail from the
> > >>   main TC list;
> > > Can you please follow up with OASIS?
> > 
> > Well, it's not like we've been sitting idle and not been following up...
> > 
> Sure. Not sure why I sounded that way. I am sorry about it.
> You mentioned you didn't know current status; this is why I asked if you can check the current status.
> I see your voted for #03820, so I assumed that you got the email. :)
> 
> > >
> > >> given that the ballot approving use of the new lists has
> > >>   not gotten a vote from several usually reliable voters, I fear that
> > >>   mail delivery regarding ballots is broken for some people as well...
> > >>
> > > I have followed up with OASIS for several of the members to fix their voting
> > and other broken access rights.
> > > Are you following up for the rest, or should I? Please let me know.
> > 
> > People have to tell me for me to do anything. If voting is not working,
> > please let the chairs know. I don't want to start another ballot if some
> > people are unable to participate.
> > 
> So it is working for 17 out of 19 voters as they voted in the latest ballot.
> If the person does not get any emails from OASIS main list, it is likely doesn't get the ballot email too.


No, ballots are mailed directly not through the list.

> And they wouldn't know that they were supposed to vote, until someone tells them.
> 
> This is why I asked if you want to follow up.
> I followed up with many to get their login etc sorted out.
> 
> > >
> > > To my knowledge, voting is broken for Enrico Granata based on the ballot
> > #03820 and previous ballot #184, #189 etc.
> > > Which other reliable voters are we missing?
> > >
> > >> Before requesting a Special Majority Vote, IMNSHO we need to be sure that
> > >> voters actually get notified about it. [We have raised the issues with mail
> > >> delivery with OASIS staff, but I'm really unsure about the current status.]
> > >>
> > > Can you please check the current status with OASIS?
> > > The migration by them is completed in March more than 2 months ago.
> > 
> > The migration is "finished", problems persist, OASIS has been notified
> > multiple times. I, as a chair, do not consider myself fully
> > operational. The joys of outsourcing.
> > 
> What are the missing things for you to be operational, maybe I can follow up on your behalf with OASIS?
> If that reduces your load...
> 
> > >
> > >> virtio-comment subscribers who are TC members as well: if you didn't get
> > any
> > >> emails from either the main TC mailing list (you can check the
> > >> archives) or from the voting platform, we'd like to hear about it.
> > >
> > > Contributors are not blocked anymore as the reviews have started already
> > with new list, which is good.
> > > Your previous recommendation of using the branch 1.4 for all the spec
> > patches, likely still stays the same. Right?
> > >
> > > [1] https://lists.oasis-open.org/archives/virtio-
> > comment/202401/msg00087.html
> > 
> > Yes, as long as we have not finalized 1.3, patches need to target
> > 1.4. Yes, it's a mess, and I'm highly frustrated.
> 
> Ok. got it. Thanks for the quick confirmation.

Re: [PATCH v3] README.md: update mailing list info

[Stefano Garzarella]

On Wed, May 15, 2024 at 05:53:14AM GMT, Michael S. Tsirkin wrote:
>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 <mst@redhat.com>
>---
>
>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(-)

Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>