Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Subject: [virtio] [PATCH] README.md: document github use
Date: Mon, 22 Jul 2019 16:39:39 -0400	[thread overview]
Message-ID: <20190722203854.16494-1-mst@redhat.com> (raw)

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 README.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/README.md b/README.md
index 3de0c1e..0aceb75 100644
--- a/README.md
+++ b/README.md
@@ -69,6 +69,34 @@ in <A
 HREF="https://github.com/oasis-tcs/virtio-admin">https://github.com/oasis-tcs/virtio-admin</A>.
 
 </div>
+<h4>Use of github issues</h4>
+Note: according to the virtio TC rules, all official TC communication
+is taking on one of the TC mailing lists.
+In particular, all comments must be provided on
+one of the TC mailing lists. Accordingly, the TC will not respond
+to comments provided in github issues: github issues are
+used solely to track integration of comments into the
+specification.<p>
+To request a TC vote on resolving a specific comment:
+<ol>
+<li>Create a github issue, or edit an existing issue, with
+a short summary of the comment.
+The issue MUST specify
+the link to the latest proposal in the TC mailing list
+archives. <em>Note:</em> the link MUST be in the issue description itself -
+<em>not</em> in the comments.</li>
+<li>Reply by email to the comment email, requesting that the TC vote
+on resolving the issue.
+The mail requesting the vote should include the following, on a line by itself:<br>
+<code>
+Fixes: https://github.com/oasis-tcs/virtio-spec/issues/NNN
+</code>
+(NNN is the issue number)</li>
+<li>Please make sure to allow time after a comment resolving
+an issue is posted and
+before asking for a vote.</li>
+</ol>
+
 <h3>Contact</h3>
 <p>Please send questions or comments about <a href="https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work">OASIS TC GitHub repositories</a> to <a href="mailto:robin@oasis-open.org">Robin Cover</a> and <a href="mailto:chet.ensign@oasis-open.org">Chet Ensign</a>.  For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the virtio TC's <a href="https://www.oasis-open.org/committees/virtio/">home page</a>.</p>
 </div>
-- 
MST

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


             reply	other threads:[~2019-07-22 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 20:39 Michael S. Tsirkin [this message]
2019-07-23  8:05 ` [virtio] [PATCH] README.md: document github use Cornelia Huck
2019-07-23 13:16 ` [virtio] Re: [virtio-dev] " Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190722203854.16494-1-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox