OASIS Virtual I/O Device (VIRTIO) TC

 View Only

[PATCH PLEASE READ] virtio/README.md: update mailing list info

  • 1.  [PATCH PLEASE READ] virtio/README.md: update mailing list info

    Posted 05-13-2024 07:36
    As approved by the TC, we are adding support for informal
    discussions around the specification to take place
    on the mailing lists provided by the Linux Foundation:

    https://groups.oasis-open.org/higherlogic/ws/public/ballot?id=3820

    Update README.md accordingly.

    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    ---

    Note that one shouldn't normally copy all mailing list like I did
    here ;) Seems justified in this case given it's admin stuff.

    README.md | 25 ++++++++++++++-----------
    1 file changed, 14 insertions(+), 11 deletions(-)

    diff --git a/README.md b/README.md
    index 2bdf485..4dd341c 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,7 +107,7 @@ 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-*

    Note for TC Members


    TC Members should review TC specific
    @@ -116,11 +117,13 @@ 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
    --
    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>