virtio — archive

[PATCH] README.md: document github use

From: Cornelia Huck <[email protected]>
To: [email protected]
Date: Tue, 23 Jul 2019 08:05:00 -0000

On Mon, 22 Jul 2019 16:39:39 -0400
"Michael S. Tsirkin" <[email protected]> wrote:

> Signed-off-by: Michael S. Tsirkin <[email protected]>
> ---
> 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.

"is taking place" ?

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

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

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.

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)

Please make sure to allow time after a comment resolving
> +an issue is posted and
> +before asking for a vote.

> +
>

Contact

Please send questions or comments about OASIS TC GitHub repositories to Robin Cover and Chet Ensign. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the virtio TC's home page.