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.
This repository documents development processes and hosts the tools used by the OASIS Virtual I/O Device (VIRTIO) Technical Committee. See also the resources in the virtio-spec and virtio-docs TC GitHub repositories
VIRTIO describes describes the specifications of the "virtio" family of devices. These devices are found in virtual environments, yet by design they look like physical devices to the guest within the virtual machine — and this document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms.
The purpose of VIRTIO and this specification is that virtual environments and guests should have a straightforward, efficient, standard and extensible mechanism for virtual devices, rather than boutique per-environment or per-OS mechanisms.
As stated in this repository's CONTRIBUTING file, contributors to this repository are expected to be Members of the OASIS VIRTIO TC, for any substantive change requests. Anyone wishing to contribute to this GitHub project and participate in the TC's technical activity is invited to join as an OASIS TC Member. Public feedback is also accepted, subject to the terms of the OASIS Feedback License.
Please see the LICENSE file for description of the license terms and OASIS policies applicable to the TC's work in this GitHub project. Content in this repository is intended to be part of the VIRTIO TC's permanent record of activity, visible and freely available for all to use, subject to applicable OASIS policies, as presented in the repository LICENSE file.
Clarification of OASIS TC process as applied to the Virtio TC: Further Description of this Repository
- 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.
- 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.
- Maintaining Voting Rights
A Voting Member who fails to cast a ballot in two consecutive Work Product
Ballots for which the voting periods do not overlap loses the voting rights at
the close of the second ballot missed. In case of multiple ballots taking place
simultaneously, voting in a single ballot is sufficient to maintain voting
Note: to avoid losing voting rights due to an extended absence, A Voting Member can request a leave of absence.
- Leave of Absence
To avoid losing voting rights due to an extended absence,
Every Voting Member can request a leave of absence.
A Leave of
Absence shall not exceed 45 days. Each request shall be made by sending an
email to the TC mailing list at least 7 days before the Leave is to start.
The TC has resolved that all such requests are automatically approved.
- Disclosure Obligations
This TC operates under the
of the OASIS IPR Policy.
The policy includes a disclosure obligation (see
OASIS IPR Policy
To satisfy the disclosure obligation, disclosures should be submitted to the virtio mailing list or the virtio-comment mailing list.
Disclosures will be uploaded to virtio-admin repository