RE: [PATCH v3] README.md: update mailing list info

[Cornelia Huck <cohuck@redhat.com>]

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/msg00087.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...

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

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

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