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=3820Update README.md accordingly.
Use this opportunity to explain when and how to use each
mailing list.
Signed-off-by: Michael S. Tsirkin <
mst@redhat.com>
---
README.md | 80 +++++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 69 insertions(+), 11 deletions(-)
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 the mailing list archives.
+To provide feedback, subscribe by sending mail to
+<href="mailto:virtio-comment+subscribe@lists.linux.dev">virtio-comment+subscribe@lists.linux.dev,
+then after confirming you agree to the IPR sending your feedback to
+<href="mailto:virtio-comment@lists.linux.dev">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 the mailing list archives.
+To participate in the discussion, subscribe by sending mail to
+<href="mailto:virtio-dev+subscribe@lists.linux.dev">
+virtio-dev+subscribe@lists.linux.dev.
+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.
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.
--
MST</href="mailto:virtio-dev@lists.linux.dev"></href="mailto:virtio-dev+subscribe@lists.linux.dev"></href="mailto:virtio-comment@lists.linux.dev"></href="mailto:virtio-comment+subscribe@lists.linux.dev"></
mst@redhat.com>