Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Gordeev <alexander.gordeev@opensynergy.com>,
	virtio-comment <virtio-comment@lists.linux.dev>
Subject: Re: [RFC] Process to request a vote for an issue
Date: Fri, 31 May 2024 13:03:55 +0200	[thread overview]
Message-ID: <87ikyumeec.fsf@redhat.com> (raw)
In-Reply-To: <b833b3f6-fad6-44a0-a67e-f1cedeeba03b@opensynergy.com>

On Fri, May 31 2024, Alexander Gordeev <alexander.gordeev@opensynergy.com> wrote:

> Hi Cornelia,
>
> On 28.05.24 14:51, Cornelia Huck wrote:
>> [first of all: there are still issues with our usage of the platform...]
>> 
>> [Also, first discussing this on virtio-comment, as this is (a) where
>> people who want to submit changes usually are subscribed, and (b) an
>> actually working list, unlike the list for the TC...]
>> 
>> The current process to include an update in the spec is something like
>> the following:
>> - open a github issue
>> - post a patch on the list, link it from the issue
>>    - iterate through some review cycles
>> - ask for a vote, so that the Chairs will open a ballot
>> 
>> The last step currently mostly happens in the thread for the latest
>> revision; such an email is easily missed if you're not actively
>> following the discussion. IMHO it isn't a very reasonable expectation
>> for the chairs to follow each and every discussion in detail; at some
>> point, it is much more reasonable to expect trusted reviewers and SMEs
>> to reach a consensus.
>> 
>> Therefore, I propose that
>> - request for votes be posted in a new, separate thread, referring to
>>    the version proposed for inclusion and ideally containing a note on
>>    who deems this proposal ready for inclusion,
>> - and those requests be clearly marked in the subject, for example with
>>    a "[Request for vote]" prefix that can be easily filtered for.
>> 
>> Thoughts, comments?
>
> Could you please specify who an SME is? Does this stand for the Society 
> of Manufacturing Engineers (sme.org)?
> I tried to search the virtio-comment and virtio-dev archives, but 
> couldn't find anything relevant:
> https://lore.kernel.org/virtio-comment/?q=SME
> https://lore.kernel.org/virtio-dev/?q=SME
> Also not in the spec repository.

SME == Subject Matter Expert

I was simply trying to describe the reality: we have people familiar
with virtio and the spec, and we have people familiar with with
technologies, and in the ideal case, we'd have both agree on a change
(can obviously be one person, if they're familiar with both :)

/me thinks she should never have brought that up and thought that was a
very common TLA :(


  reply	other threads:[~2024-05-31 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 12:51 [RFC] Process to request a vote for an issue Cornelia Huck
2024-05-28 13:05 ` Parav Pandit
2024-05-28 13:29   ` Cornelia Huck
2024-05-28 13:46     ` Parav Pandit
2024-05-28 14:09       ` Cornelia Huck
2024-05-28 14:39         ` Parav Pandit
2024-05-29 16:14           ` Cornelia Huck
2024-05-31 10:39 ` Alexander Gordeev
2024-05-31 11:03   ` Cornelia Huck [this message]
2024-06-05  7:19     ` Alexander Gordeev

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=87ikyumeec.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alexander.gordeev@opensynergy.com \
    --cc=virtio-comment@lists.linux.dev \
    /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