Merge https://github.com/oasis-tcs/virtio-spec into trunk

This merges in the OASIS boilerplate files in preparation to
moving virtio spec development to git, as approved at:

https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=3120

Files added:

CONTRIBUTING.md
LICENSE.md
README.md

TODO: tweak boilerplate files as appropriate/needed.

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

1 files changed, 20 insertions, 0 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..1330a98
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,20 @@
+<div>
+<h2>Repository Contributions, Participation, and Public Access</h2>
+
+<p><b>Who may Contribute?</b> Contributors to <a href="https://github.com/oasis-tcs/virtio-spec/">this repository</a> are expected to be <a href="https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2017-05-26#dMember">Members</a> of the
+<a href="https://www.oasis-open.org/committees/virtio/">OASIS Virtual I/O Device (VIRTIO) TC</a>, for any
+substantive contributions.  Anyone wishing to <a href="https://www.oasis-open.org/org/faq#committee-participation">participate</a>
+in the TC's technical activity is invited to <a href="https://www.oasis-open.org/committees/join">join</a> as a TC Member.
+<i>Member</i> in this context means any TC role or office other than OASIS TC Observer, per
+<a href="https://www.oasis-open.org/policies-guidelines/tc-process#membership">TC Process</a>
+(Member, Voting Member, Persistent Non-Voting Member; Chair, Secretary...)</p>
+
+<p>Persons who are not TC members are invited to open issues and provide comments using this repository's <a href="https://github.com/oasis-tcs/virtio-spec/issues/new">GitHub Issues</a> tracking facility or using the
+TC's <a href="https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio">comment list</a>.  All such content created in GitHub Issues and/or posted to the TC's <a href="https://lists.oasis-open.org/archives/virtio-comment/">archived comment list</a> is governed by the terms of the <a href="https://www.oasis-open.org/policies-guidelines/ipr#appendixa">OASIS Feedback License</a>.</p>
+
+<p><b>Use of Contributions</b>.  As with all OASIS Technical Committee assets (TC <a href="https://wiki.oasis-open.org/">Wiki</a>, TC <a href="https://issues.oasis-open.org/secure/Dashboard.jspa">Issues Tracker</a>, TC <a href="https://lists.oasis-open.org/archives/">General Discussion List archives</a>, TC <a href="http://docs.oasis-open.org/">OASIS Library</a> assets), content placed into this GitHub repository is visible and publicly accessible.  Subject to applicable <a href="https://github.com/oasis-tcs/virtio-spec/blob/master/LICENSE.md">licensing</a> rules, the repository content may be re-used freely, including the creation and publication of derivative works.</p>
+
+<p><b>Cloning and forking</b>. May users clone and fork this repository?  Yes. Just as versioned content maintained in any OASIS TC's <a href="https://tools.oasis-open.org/version-control/browse/">SVN/Subversion repository</a> may be checked out to a remote SVN repository and used by anyone, this GitHub repository may be forked or cloned for use by any party.  Compare, <i>e.g.</i>, <tt>svn checkout https://tools.oasis-open.org/version-control/svn/dita/trunk/doctypes/ dita-doctypes</tt>.</p>
+
+<p>Please see the <a href="https://github.com/oasis-tcs/virtio-spec/blob/master/README.md">README</a> for general description of this repository, and the <a href="https://github.com/oasis-tcs/virtio-spec/blob/master/LICENSE.md">LICENSE</a> file for licensing.</p>
+</div>