From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>
Subject: Re: [PATCH v3] README.md: update mailing list info
Date: Tue, 21 May 2024 10:32:52 -0400 [thread overview]
Message-ID: <20240521103210-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB548123CFB2F493A79CE15271DCEA2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, May 21, 2024 at 01:24:25PM +0000, Parav Pandit wrote:
>
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Tuesday, May 21, 2024 6:13 PM
> >
> > On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> >
> > >> From: Cornelia Huck <cohuck@redhat.com>
> > >> Sent: Tuesday, May 21, 2024 3:29 PM
> > >>
> > >> On Tue, May 21 2024, Parav Pandit <parav@nvidia.com> wrote:
> > >>
> > >> >> From: Michael S. Tsirkin <mst@redhat.com>
> > >> >> Sent: Tuesday, May 21, 2024 12:55 PM
> > >> >>
> > >> >> On Tue, May 21, 2024 at 04:19:31AM +0000, Parav Pandit wrote:
> > >> >> > Hi Michael,
> > >> >> >
> > >> >> > > From: Michael S. Tsirkin <mst@redhat.com>
> > >> >> > > Sent: Wednesday, May 15, 2024 4:07 PM
> > >> >> >
> > >> >> > > > > I would wait until next Monday at least. Give everyone
> > >> >> > > > > time to subscribe to the new list.
> > >> >> >
> > >> >> > Can you please merge this patch?
> > >> >>
> > >> >> Pushed now.
> > >> >
> > >> > Thanks Michael.
> > >> > Cornelia mentioned in [1] that master and 1.4 should be merged.
> > >> > 1.4 is 17 patches behind the master including this one.
> > >> > And 12 commits behind..
> > >> >
> > >> > Can you please merge them? Without it, there are conflicts in patches.
> > >> >
> > >> > Also, we need to update in the README.md on which branch to use for
> > >> sending the patches.
> > >> >
> > >> > [1]
> > >> > https://lists.oasis-open.org/archives/virtio-comment/202401/msg0008
> > >> > 7.h
> > >> > tml
> > >>
> > >> Repo status is a mess, because the state of the TC is currently a mess...
> > >>
> > >> * Before we can merge the branches, we need to do a proper Special
> > >> Majority Vote to release 1.3 (which had been delayed since *last year*
> > >> due to first the threatening migration, and then the actual
> > >> troublesome migration.)
> > >> * The platform is still not working properly. For starters, we now know
> > >> that other people besides myself are not getting any mail from the
> > >> main TC list;
> > > Can you please follow up with OASIS?
> >
> > Well, it's not like we've been sitting idle and not been following up...
> >
> Sure. Not sure why I sounded that way. I am sorry about it.
> You mentioned you didn't know current status; this is why I asked if you can check the current status.
> I see your voted for #03820, so I assumed that you got the email. :)
>
> > >
> > >> given that the ballot approving use of the new lists has
> > >> not gotten a vote from several usually reliable voters, I fear that
> > >> mail delivery regarding ballots is broken for some people as well...
> > >>
> > > I have followed up with OASIS for several of the members to fix their voting
> > and other broken access rights.
> > > Are you following up for the rest, or should I? Please let me know.
> >
> > People have to tell me for me to do anything. If voting is not working,
> > please let the chairs know. I don't want to start another ballot if some
> > people are unable to participate.
> >
> So it is working for 17 out of 19 voters as they voted in the latest ballot.
> If the person does not get any emails from OASIS main list, it is likely doesn't get the ballot email too.
No, ballots are mailed directly not through the list.
> And they wouldn't know that they were supposed to vote, until someone tells them.
>
> This is why I asked if you want to follow up.
> I followed up with many to get their login etc sorted out.
>
> > >
> > > To my knowledge, voting is broken for Enrico Granata based on the ballot
> > #03820 and previous ballot #184, #189 etc.
> > > Which other reliable voters are we missing?
> > >
> > >> Before requesting a Special Majority Vote, IMNSHO we need to be sure that
> > >> voters actually get notified about it. [We have raised the issues with mail
> > >> delivery with OASIS staff, but I'm really unsure about the current status.]
> > >>
> > > Can you please check the current status with OASIS?
> > > The migration by them is completed in March more than 2 months ago.
> >
> > The migration is "finished", problems persist, OASIS has been notified
> > multiple times. I, as a chair, do not consider myself fully
> > operational. The joys of outsourcing.
> >
> What are the missing things for you to be operational, maybe I can follow up on your behalf with OASIS?
> If that reduces your load...
>
> > >
> > >> virtio-comment subscribers who are TC members as well: if you didn't get
> > any
> > >> emails from either the main TC mailing list (you can check the
> > >> archives) or from the voting platform, we'd like to hear about it.
> > >
> > > Contributors are not blocked anymore as the reviews have started already
> > with new list, which is good.
> > > Your previous recommendation of using the branch 1.4 for all the spec
> > patches, likely still stays the same. Right?
> > >
> > > [1] https://lists.oasis-open.org/archives/virtio-
> > comment/202401/msg00087.html
> >
> > Yes, as long as we have not finalized 1.3, patches need to target
> > 1.4. Yes, it's a mess, and I'm highly frustrated.
>
> Ok. got it. Thanks for the quick confirmation.
next prev parent reply other threads:[~2024-05-21 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:53 [PATCH v3] README.md: update mailing list info Michael S. Tsirkin
2024-05-15 10:14 ` Parav Pandit
2024-05-15 10:30 ` Michael S. Tsirkin
2024-05-15 10:32 ` Parav Pandit
2024-05-15 10:37 ` Michael S. Tsirkin
2024-05-21 4:19 ` Parav Pandit
2024-05-21 7:24 ` Michael S. Tsirkin
2024-05-21 7:59 ` Parav Pandit
2024-05-21 8:03 ` Michael S. Tsirkin
2024-05-21 8:06 ` Parav Pandit
2024-05-21 9:58 ` Cornelia Huck
2024-05-21 12:02 ` Parav Pandit
2024-05-21 12:07 ` Michael S. Tsirkin
2024-05-21 12:42 ` Cornelia Huck
2024-05-21 13:24 ` Parav Pandit
2024-05-21 14:32 ` Michael S. Tsirkin [this message]
2024-05-16 8:15 ` Stefano Garzarella
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=20240521103210-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).