From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.linux.dev, virtio-dev@lists.linux.dev
Subject: [PATCH v3] README.md: update mailing list info
Date: Wed, 15 May 2024 05:53:14 -0400 [thread overview]
Message-ID: <8f5db33c96d685fcebca3579b05d09b64dd720d9.1715766697.git.mst@redhat.com> (raw)
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 <email><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
next reply other threads:[~2024-05-15 9:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:53 Michael S. Tsirkin [this message]
2024-05-15 10:14 ` [PATCH v3] README.md: update mailing list info Parav Pandit
2024-05-15 10:30 ` Michael S. Tsirkin
2024-05-15 10:32 ` Parav Pandit
2024-05-15 10:37 ` Michael S. Tsirkin
2024-05-21 4:19 ` Parav Pandit
2024-05-21 7:24 ` Michael S. Tsirkin
2024-05-21 7:59 ` Parav Pandit
2024-05-21 8:03 ` Michael S. Tsirkin
2024-05-21 8:06 ` Parav Pandit
2024-05-21 9:58 ` Cornelia Huck
2024-05-21 12:02 ` Parav Pandit
2024-05-21 12:07 ` Michael S. Tsirkin
2024-05-21 12:42 ` Cornelia Huck
2024-05-21 13:24 ` Parav Pandit
2024-05-21 14:32 ` Michael S. Tsirkin
2024-05-16 8:15 ` Stefano Garzarella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f5db33c96d685fcebca3579b05d09b64dd720d9.1715766697.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=virtio-comment@lists.linux.dev \
--cc=virtio-dev@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).