virtio — archive

[Stefan Hajnoczi <mst@redhat.com>]

On Mon, Jul 22, 2019 at 04:39:39PM -0400, Michael S. Tsirkin wrote:
> 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 > HREF="https://github.com/oasis-tcs/virtio-admin">https://github.com/oasis-tcs/virtio-admin.
>
>
> +

Use of github issues

> +Note: according to the virtio TC rules, all official TC communication
> +is taking on one of the TC mailing lists.

s/is taking on/takes place on/

> +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.

This sense can be made clearer:

"github issues are used solely to track integration of comments from
the TC mailing lists into the specification"

> +To request a TC vote on resolving a specific comment:
> +

> +
1. 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. Note: the link MUST be in the issue description itself -
   > +not in the comments.


I don't understand what this note means.

> +
2. 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:
   
   > +
> +Fixes: https://github.com/oasis-tcs/virtio-spec/issues/NNN
> +
   > +(NNN is the issue number)

> +
3. Please make sure to allow time after a comment resolving
   
   Clarification:
   
   "Please make sure to allow time for review after a comment resolving
   ..."