On Wed, Apr 03, 2024 at 03:01:44PM +0000, Michael S. Tsirkin via OASIS wrote:
> On Wed, Apr 03, 2024 at 12:37:50PM +0000, Stefan Hajnoczi via OASIS wrote:
> > On Wed, Apr 03, 2024 at 10:16:02AM +0000, Cornelia Huck via OASIS wrote: >
> > [This is both a test whether I can actually send mail to the new list,...
> > OASIS Virtual I/O Device (VIRTIO) TC
> >
> > Post New Message
> >
> > Re: Current state of the infrastructure for the virtio TC
> >
> > Reply to Group Reply to Sender via
> > Email
> >
> > Stefan Apr 3, 2024 8:38 AM
> > Hajnoczi Stefan Hajnoczi
> >
> > On Wed, Apr 03, 2024 at 10:16:02AM +0000, Cornelia Huck via OASIS wrote:
> > > [This is both a test whether I can actually send mail to the new list,
> > > and an attempt to share some information on the current state of
> > > affairs...]
> > >
> > > Dear virtio TC members,
> > >
> > > we're still struggling with the migration of the OASIS infrastructure,
> > > and I wanted to at least try to give some update.
> > >
> > > As of now,
> > >
> > > * the old
virtio@lists.oasis-open.org list has been migrated to
> > >
OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> > > to.) However, there have been issues with some people (including
> > > myself, and others I've talked to) not actually receiving any emails
> > > from the new list. It might be helpful if people could check with
> > > other TC members from within their organization if they received any
> > > communication -- I assume that would also be helpful data to figure
> > > out what is going wrong;
> >
> > Hi Cornelia,
> > This is just to confirm that your email was delivered.
> >
> > Unfortunately your email address is hidden and replaced by the mailing
> > list. This means you won't be CCed on this reply. That may make it
> > harder for some of us to notice replies to threads we participate in,
> > depending on our email workflows.
> >
> > Stefan
>
> Oh my. In fact, yes
> /facepalm
Testing to see if sub-threads work on this mailing list.
(I think the answer is "no", there is just one long list of email
replies without sub-threads.)
Stefan
>
> > >
> > > * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> > > for the not-that-helpful auto-reply. They are supposed to be migrated,
> > > but we don't have any ETA. As these lists are essential to the way we
> > > develop the virtio spec, we are actively exploring how to proceed and
> > > get back to a working state ASAP;
> > >
> > > * the interface for initiating votes (unsurprisingly) changed with the
> > > new infrastructure, which means that our old admin scripts stopped
> > > working. Adapting the scripts to the new infrastructure is
> > > challenging, as we need to do web scraping and run into issues like
> > > CAPCHAs. A proper REST API would of course be preferable, and we
> > > already suggested that to OASIS, but as of now, all interaction with
> > > the web interface would need to be manual and therefore slower.
> > >
> > > As we're not sure how to reach virtio contributors reliably right now
> > > (due to the first two issues), unfortunately, no progress with either
> > > finally doing a proper release of the 1.3 spec or proceeding with the
> > > next 1.4 release is currently being made. I realize that this is very
> > > frustrating for everybody, and we've been trying to address the ongoing
> > > issues with OASIS.
> > >
> > > I hope that I can bring better news soon.
> > >
> > > Regards,
> > > Cornelia
> > >
> > > Reply to Sender : groups.oasis-open.org/eGroups/PostReply/...
> > >
> > > Reply to Discussion : groups.oasis-open.org/eGroups/PostReply/...
> > >
> > >
> > >
> > > You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as
> >
stefanha@redhat.com. To change your subscriptions, go to
> > oasis.connectedcommunity.org/... To unsubscribe from this community
> > discussion, go to oasis.connectedcommunity.org/HigherLogic/eGroups/...
> >
> >
> > Reply to Group via Email Reply to Sender via Email View Thread
> > Recommend Forward
> >
> > -------------------------------------------
> > Original Message:
> > Sent: 4/3/2024 6:16:00 AM
> > From: Cornelia Huck
> > Subject: Current state of the infrastructure for the virtio TC
> >
> > [This is both a test whether I can actually send mail to the new list,
> > and an attempt to share some information on the current state of
> > affairs...]
> >
> > Dear virtio TC members,
> >
> > we're still struggling with the migration of the OASIS infrastructure,
> > and I wanted to at least try to give some update.
> >
> > As of now,
> >
> > * the old
virtio@lists.oasis-open.org list has been migrated to
> >
OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> > to.) However, there have been issues with some people (including
> > myself, and others I've talked to) not actually receiving any emails
> > from the new list. It might be helpful if people could check with
> > other TC members from within their organization if they received any
> > communication -- I assume that would also be helpful data to figure
> > out what is going wrong;
> >
> > * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> > for the not-that-helpful auto-reply. They are supposed to be migrated,
> > but we don't have any ETA. As these lists are essential to the way we
> > develop the virtio spec, we are actively exploring how to proceed and
> > get back to a working state ASAP;
> >
> > * the interface for initiating votes (unsurprisingly) changed with the
> > new infrastructure, which means that our old admin scripts stopped
> > working. Adapting the scripts to the new infrastructure is
> > challenging, as we need to do web scraping and run into issues like
> > CAPCHAs. A proper REST API would of course be preferable, and we
> > already suggested that to OASIS, but as of now, all interaction with
> > the web interface would need to be manual and therefore slower.
> >
> > As we're not sure how to reach virtio contributors reliably right now
> > (due to the first two issues), unfortunately, no progress with either
> > finally doing a proper release of the 1.3 spec or proceeding with the
> > next 1.4 release is currently being made. I realize that this is very
> > frustrating for everybody, and we've been trying to address the ongoing
> > issues with OASIS.
> >
> > I hope that I can bring better news soon.
> >
> > Regards,
> > Cornelia
> >
> >
> >
> >
> >
> >
> > You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as
mst@redhat.com.
> > To change your subscriptions, go to My Subscriptions. To unsubscribe from this
> > community discussion, go to Unsubscribe.
> >
> > *
>
> -------------------------------------------
> Original Message:
> Sent: 4/3/2024 8:38:00 AM
> From: Stefan Hajnoczi
> Subject: RE: Current state of the infrastructure for the virtio TC
>
> On Wed, Apr 03, 2024 at 10:16:02AM +0000, Cornelia Huck via OASIS wrote:
> > [This is both a test whether I can actually send mail to the new list,
> > and an attempt to share some information on the current state of
> > affairs...]
> >
> > Dear virtio TC members,
> >
> > we're still struggling with the migration of the OASIS infrastructure,
> > and I wanted to at least try to give some update.
> >
> > As of now,
> >
> > * the old
virtio@lists.oasis-open.org list has been migrated to
> >
OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> > to.) However, there have been issues with some people (including
> > myself, and others I've talked to) not actually receiving any emails
> > from the new list. It might be helpful if people could check with
> > other TC members from within their organization if they received any
> > communication -- I assume that would also be helpful data to figure
> > out what is going wrong;
>
> Hi Cornelia,
> This is just to confirm that your email was delivered.
>
> Unfortunately your email address is hidden and replaced by the mailing
> list. This means you won't be CCed on this reply. That may make it
> harder for some of us to notice replies to threads we participate in,
> depending on our email workflows.
>
> Stefan
>
> >
> > * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> > for the not-that-helpful auto-reply. They are supposed to be migrated,
> > but we don't have any ETA. As these lists are essential to the way we
> > develop the virtio spec, we are actively exploring how to proceed and
> > get back to a working state ASAP;
> >
> > * the interface for initiating votes (unsurprisingly) changed with the
> > new infrastructure, which means that our old admin scripts stopped
> > working. Adapting the scripts to the new infrastructure is
> > challenging, as we need to do web scraping and run into issues like
> > CAPCHAs. A proper REST API would of course be preferable, and we
> > already suggested that to OASIS, but as of now, all interaction with
> > the web interface would need to be manual and therefore slower.
> >
> > As we're not sure how to reach virtio contributors reliably right now
> > (due to the first two issues), unfortunately, no progress with either
> > finally doing a proper release of the 1.3 spec or proceeding with the
> > next 1.4 release is currently being made. I realize that this is very
> > frustrating for everybody, and we've been trying to address the ongoing
> > issues with OASIS.
> >
> > I hope that I can bring better news soon.
> >
> > Regards,
> > Cornelia
> >
> > Reply to Sender :
https://groups.oasis-open.org/eGroups/PostReply/?GroupId=2767&MID=495539&SenderKey=27866af1-5c9f-43da-8008-018dc7e5aaac> >
> > Reply to Discussion :
https://groups.oasis-open.org/eGroups/PostReply/?GroupId=2767&MID=495539> >
> >
> >
> > You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as
stefanha@redhat.com. To change your subscriptions, go to
http://oasis.connectedcommunity.org/preferences?section=Subscriptions. To unsubscribe from this community discussion, go to
http://oasis.connectedcommunity.org/HigherLogic/eGroups/Unsubscribe.aspx?UserKey=7dcf8429-ea1f-4724-a0bf-018dc99ec7d6&sKey=KeyRemoved&GroupKey=c337f117-a176-45c6-96cb-018dce2b6955.>
> -------------------------------------------
> Original Message:
> Sent: 4/3/2024 6:16:00 AM
> From: Cornelia Huck
> Subject: Current state of the infrastructure for the virtio TC
>
> [This is both a test whether I can actually send mail to the new list,
> and an attempt to share some information on the current state of
> affairs...]
>
> Dear virtio TC members,
>
> we're still struggling with the migration of the OASIS infrastructure,
> and I wanted to at least try to give some update.
>
> As of now,
>
> * the old
virtio@lists.oasis-open.org list has been migrated to
>
OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> to.) However, there have been issues with some people (including
> myself, and others I've talked to) not actually receiving any emails
> from the new list. It might be helpful if people could check with
> other TC members from within their organization if they received any
> communication -- I assume that would also be helpful data to figure
> out what is going wrong;
>
> * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> for the not-that-helpful auto-reply. They are supposed to be migrated,
> but we don't have any ETA. As these lists are essential to the way we
> develop the virtio spec, we are actively exploring how to proceed and
> get back to a working state ASAP;
>
> * the interface for initiating votes (unsurprisingly) changed with the
> new infrastructure, which means that our old admin scripts stopped
> working. Adapting the scripts to the new infrastructure is
> challenging, as we need to do web scraping and run into issues like
> CAPCHAs. A proper REST API would of course be preferable, and we
> already suggested that to OASIS, but as of now, all interaction with
> the web interface would need to be manual and therefore slower.
>
> As we're not sure how to reach virtio contributors reliably right now
> (due to the first two issues), unfortunately, no progress with either
> finally doing a proper release of the 1.3 spec or proceeding with the
> next 1.4 release is currently being made. I realize that this is very
> frustrating for everybody, and we've been trying to address the ongoing
> issues with OASIS.
>
> I hope that I can bring better news soon.
>
> Regards,
> Cornelia
>
> Reply to Sender :
https://groups.oasis-open.org/eGroups/PostReply/?GroupId=2767&MID=495543&SenderKey=a2b58e24-6eaa-4c47-a934-018dc916b912>
> Reply to Discussion :
https://groups.oasis-open.org/eGroups/PostReply/?GroupId=2767&MID=495543>
>
>
> You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as
stefanha@redhat.com. To change your subscriptions, go to
http://oasis.connectedcommunity.org/preferences?section=Subscriptions. To unsubscribe from this community discussion, go to
http://oasis.connectedcommunity.org/HigherLogic/eGroups/Unsubscribe.aspx?UserKey=7dcf8429-ea1f-4724-a0bf-018dc99ec7d6&sKey=KeyRemoved&GroupKey=c337f117-a176-45c6-96cb-018dce2b6955.
Original Message:
Sent: 4/3/2024 11:02:00 AM
From: Michael S. Tsirkin
Subject: RE: Current state of the infrastructure for the virtio TC
On Wed, Apr 03, 2024 at 12:37:50PM +0000, Stefan Hajnoczi via OASIS wrote:
> On Wed, Apr 03, 2024 at 10:16:02AM +0000, Cornelia Huck via OASIS wrote: >
> [This is both a test whether I can actually send mail to the new list,...
> OASIS Virtual I/O Device (VIRTIO) TC
>
> Post New Message
>
> Re: Current state of the infrastructure for the virtio TC
>
> Reply to Group Reply to Sender via
> Email
>
> Stefan Apr 3, 2024 8:38 AM
> Hajnoczi Stefan Hajnoczi
>
> On Wed, Apr 03, 2024 at 10:16:02AM +0000, Cornelia Huck via OASIS wrote:
> > [This is both a test whether I can actually send mail to the new list,
> > and an attempt to share some information on the current state of
> > affairs...]
> >
> > Dear virtio TC members,
> >
> > we're still struggling with the migration of the OASIS infrastructure,
> > and I wanted to at least try to give some update.
> >
> > As of now,
> >
> > * the old virtio@lists.oasis-open.org list has been migrated to
> > OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> > to.) However, there have been issues with some people (including
> > myself, and others I've talked to) not actually receiving any emails
> > from the new list. It might be helpful if people could check with
> > other TC members from within their organization if they received any
> > communication -- I assume that would also be helpful data to figure
> > out what is going wrong;
>
> Hi Cornelia,
> This is just to confirm that your email was delivered.
>
> Unfortunately your email address is hidden and replaced by the mailing
> list. This means you won't be CCed on this reply. That may make it
> harder for some of us to notice replies to threads we participate in,
> depending on our email workflows.
>
> Stefan
Oh my. In fact, yes
/facepalm
> >
> > * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> > for the not-that-helpful auto-reply. They are supposed to be migrated,
> > but we don't have any ETA. As these lists are essential to the way we
> > develop the virtio spec, we are actively exploring how to proceed and
> > get back to a working state ASAP;
> >
> > * the interface for initiating votes (unsurprisingly) changed with the
> > new infrastructure, which means that our old admin scripts stopped
> > working. Adapting the scripts to the new infrastructure is
> > challenging, as we need to do web scraping and run into issues like
> > CAPCHAs. A proper REST API would of course be preferable, and we
> > already suggested that to OASIS, but as of now, all interaction with
> > the web interface would need to be manual and therefore slower.
> >
> > As we're not sure how to reach virtio contributors reliably right now
> > (due to the first two issues), unfortunately, no progress with either
> > finally doing a proper release of the 1.3 spec or proceeding with the
> > next 1.4 release is currently being made. I realize that this is very
> > frustrating for everybody, and we've been trying to address the ongoing
> > issues with OASIS.
> >
> > I hope that I can bring better news soon.
> >
> > Regards,
> > Cornelia
> >
> > Reply to Sender : groups.oasis-open.org/eGroups/PostReply/...
> >
> > Reply to Discussion : groups.oasis-open.org/eGroups/PostReply/...
> >
> >
> >
> > You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as
> stefanha@redhat.com. To change your subscriptions, go to
> oasis.connectedcommunity.org/... To unsubscribe from this community
> discussion, go to oasis.connectedcommunity.org/HigherLogic/eGroups/...
>
>
> Reply to Group via Email Reply to Sender via Email View Thread
> Recommend Forward
>
> -------------------------------------------
> Original Message:
> Sent: 4/3/2024 6:16:00 AM
> From: Cornelia Huck
> Subject: Current state of the infrastructure for the virtio TC
>
> [This is both a test whether I can actually send mail to the new list,
> and an attempt to share some information on the current state of
> affairs...]
>
> Dear virtio TC members,
>
> we're still struggling with the migration of the OASIS infrastructure,
> and I wanted to at least try to give some update.
>
> As of now,
>
> * the old virtio@lists.oasis-open.org list has been migrated to
> OASIS-virtio@ConnectedCommunity.org (the list I'm attempting to send
> to.) However, there have been issues with some people (including
> myself, and others I've talked to) not actually receiving any emails
> from the new list. It might be helpful if people could check with
> other TC members from within their organization if they received any
> communication -- I assume that would also be helpful data to figure
> out what is going wrong;
>
> * the old virtio-comment@ and virtio-dev@ lists are currently dead save
> for the not-that-helpful auto-reply. They are supposed to be migrated,
> but we don't have any ETA. As these lists are essential to the way we
> develop the virtio spec, we are actively exploring how to proceed and
> get back to a working state ASAP;
>
> * the interface for initiating votes (unsurprisingly) changed with the
> new infrastructure, which means that our old admin scripts stopped
> working. Adapting the scripts to the new infrastructure is
> challenging, as we need to do web scraping and run into issues like
> CAPCHAs. A proper REST API would of course be preferable, and we
> already suggested that to OASIS, but as of now, all interaction with
> the web interface would need to be manual and therefore slower.
>
> As we're not sure how to reach virtio contributors reliably right now
> (due to the first two issues), unfortunately, no progress with either
> finally doing a proper release of the 1.3 spec or proceeding with the
> next 1.4 release is currently being made. I realize that this is very
> frustrating for everybody, and we've been trying to address the ongoing
> issues with OASIS.
>
> I hope that I can bring better news soon.
>
> Regards,
> Cornelia
>
>
>
>
>
>
> You are subscribed to "OASIS Virtual I/O Device (VIRTIO) TC" as mst@redhat.com.
> To change your subscriptions, go to My Subscriptions. To unsubscribe from this
> community discussion, go to Unsubscribe.
>
> *