All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: virtio-comment <virtio-comment@lists.linux.dev>
Subject: [RFC] Process to request a vote for an issue
Date: Tue, 28 May 2024 14:51:15 +0200	[thread overview]
Message-ID: <87plt6nlq4.fsf@redhat.com> (raw)

[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?


             reply	other threads:[~2024-05-28 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 12:51 Cornelia Huck [this message]
2024-05-28 13:05 ` [RFC] Process to request a vote for an issue 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
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=87plt6nlq4.fsf@redhat.com \
    --to=cohuck@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.