|
Should the TC switch specification development from git-svn to git?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to request opening a github repository
for Virtio TC Members' chartered work, as described here:
https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work
List of repository maintainers - same as list of editors with svn access:
Michael S. Tsirkin, Cornelia Huck, Pawel Moll
List of repositories to request:
virtio-spec
- specification sources
virtio-docs
- compiled copies of the spec
virtio-admin
- documentation on virtio tc workings
The TC agrees that all future specification development will switch from OASIS
SVN to the virtio-spec github repository. README.txt file in the SVN repository
will be updated to point at the github repository. A file with a name similar
to NOT_IN_USE_SEE_README.txt will be placed at the root of the SVN repository,
to direct users at the correct location.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|
