OASIS Virtual I/O Device (VIRTIO) TC

 View Only

[PATCH v4] virtio-admin: README.md: misc fixes

  • 1.  [PATCH v4] virtio-admin: README.md: misc fixes

    Posted 04-23-2025 01:53
    Some small corrections:
    - update links to point to the new OASIS page
    - mention virtio comment is subscriber only
    - replace chair->chairs as we have several now
    - a typo fix

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

    changes from v3:
    go back to using old charter link, at oasis request

    README.md | 16 ++++++++--------
    1 file changed, 8 insertions(+), 8 deletions(-)

    diff --git a/README.md b/README.md
    index 1fed245..cede10f 100644
    --- a/README.md
    +++ b/README.md
    @@ -1,7 +1,7 @@

    README



    -

    Members of the OASIS Virtual I/O Device (VIRTIO) TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/virtio-admin ) as part of the TC's chartered work (i.e., the program of work and deliverables described in its charter).


    +

    Members of the OASIS Virtual I/O Device (VIRTIO) TC create and manage technical content in this TC GitHub repository ( https://github.com/oasis-tcs/virtio-admin ) as part of the TC's chartered work (i.e., the program of work and deliverables described in its charter).



    OASIS TC GitHub repositories, as described in GitHub Repositories for OASIS TC Members' Chartered Work, are governed by the OASIS TC Process, IPR Policy, and other policies, similar to TC Wikis, TC JIRA issues tracking instances, TC SVN/Subversion repositories, etc. While they make use of public GitHub repositories, these TC GitHub repositories are distinct from OASIS Open Repositories, which are used for development of open source licensed content.



    @@ -36,15 +36,15 @@
    Virtio TC Meetings:

    The Virtio TC has adopted a standing rule to conduct business only by electronic ballot, without Meetings.
    The list of all current and past ballots can be found on
    -this page.
    +this page.

    Gaining voting rights

    A TC Member who lacks voting rights shall only gain voting rights
    after requesting this from the TC chair by submitting the request to the
    - virtio mailing list
    - with a copy sent to the TC chair by email. For example, for a new TC member
    - to gain voting rights the request shall be send to the TC
    - chair after the close of the 60th day.
    + OASIS-virtio@connectedcommunity.org mailing list
    + with a copy sent to the TC chairs by email. For example, for a new TC member
    + to gain voting rights the request shall be sent to the TC
    + chairs after the close of the 60th day.

    Maintaining Voting Rights


    @@ -75,8 +75,8 @@ The policy includes a disclosure obligation (see
    for details).


    To satisfy the disclosure obligation, disclosures should be submitted to
    -the virtio mailing list
    -or the virtio-comment mailing list.
    +the OASIS-virtio@connectedcommunity.org mailing list
    +or the virtio-comment@lists.linux.dev mailing list (subscriber only).


    Disclosures will be uploaded to
    virtio-admin repository
    --
    MST
    </mst@redhat.com>