From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.linux.dev
Subject: [mst@redhat.com: virtio TC: nominating additional co-editor and co-chair]
Date: Thu, 10 Oct 2024 12:35:19 -0400 [thread overview]
Message-ID: <20241010123439-mutt-send-email-mst@kernel.org> (raw)
The following was send to a virtio TC members-only list.
Copying here for the sake of transparency.
----- Forwarded message from "Michael S. Tsirkin" <mst@redhat.com> -----
From: "Michael S. Tsirkin" <mst@redhat.com>
Date: Thu, 10 Oct 2024 10:42:12 -0400
To: OASIS-virtio@connectedcommunity.org
Subject: virtio TC: nominating additional co-editor and co-chair
Message-ID: <20241010101823-mutt-send-email-mst@kernel.org>
Hello!
Two important roles in the TC are an editor and a chair. Currently both
Cornelia Huck and me are editors and chairs. With the volume of
contributions increasing, the current editors and chairs felt overloaded
and were looking to get help. After some internal discussion, and
reviewing contribution history, two candidates were proposed, the
description below.
Within the virtio TC, the chair is responsible for creating voting
ballots. Since the situation where the TC approved a spec change,
only to find there is an issue with the change later, is messy to
resolve, the chair is also responsible for reviewing patches
for functional correctness and clarify,
tracking TC discussion and making sure the change was reviewed
before the ballot starts.
Matias Ezequiel Vara Larsen has been active in reviewing multiple
contributions, and volunteered for a role on an additional co-chair.
The editor is responsible for submitting the approved changes into the
git repository. Within the virtio TC, this also includes making
editorial fixes: fixing typos and such. The editor is also responsible
for making sure the result compiles into alternative formats (PDF,
HTML), compiling final revisions for public review (clean and redlined)
and release.
Parav Pandit has been active in making multiple such editorial
fixes, and volunteered for this role.
The fact that the new co-chair can not commit directly, while the new
co-editor can not start a vote directly, should serve to keep some
checks and balances in place, and allow the community to keep working
smoothly.
Finally, we might have overlooked someone active in patch review or making
editorial fixes. Feel free to reach out by a private message if you
feel you have been active in one of those roles and would like to
volunteer.
There's no limit on number of chairs or editors, we can add more.
For now, I started two ballots to approve the two nominations, if you are a voting member,
you will be able to find both ballots here:
https://groups.oasis-open.org/higherlogic/ws/groups/b3f5efa5-0e12-4320-873b-018dc7d3f25c/ballots
As a reminder, ballot participation is mandatory to maintain voting rights.
--
MST
----- End forwarded message -----
reply other threads:[~2024-10-10 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241010123439-mutt-send-email-mst@kernel.org \
--to=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox