virtio — archive

[Halil Pasic]

On 08/02/2018 12:30 AM, Michael S. Tsirkin wrote: > On Wed, Aug 01, 2018 at 03:04:54PM +0200, Halil Pasic wrote: >> >> >> On 07/27/2018 01:45 PM, Michael S. Tsirkin wrote: >>> On Fri, Jul 27, 2018 at 01:33:15PM +0200, Halil Pasic wrote: >>>> >>>> >>>> On 07/17/2018 06:47 PM, Halil Pasic wrote: >>>>>>>> >>>>>>>> OK I see there are acks already - do you want to start voting on this? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Yes, voting would make sense in my opinion. >>>>>>> >>>>>> >>>>>> >>>>>> I've submitted a github issue. Please let me know if further actions are >>>>>> required. >>>>>> >>>>> >>>>> ping >>>> >>>> ping >>> >>> Oh, sorry, I wasn't clear. >>> What you want to do is >>> 1. post the patches including >>> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/16 >>> in the commit log part. >>> 2. proposal must link to oasis archive, not mail-archive. >>> >>> Anyway, I fixed the link and started voting now. >>> >> >> Should post a v4 (or a 'REPOST v3') with the r-b's received for >> v3 and the 'Fixes' tags? I mean the ballot, would not link to the >> final thread then. I'm a bit confused regarding now, but I >> think I understood the process. > > I think you are right since ballot started no need for v4. > Thanks! >> FYI I'm on and off starting tomorrow till 5th September. I >> am very likely to make any ballots though, but longer response >> times and lower availability are to be expected. >> >> Thanks, >> Halil > > What are we going to do about crypto proposals? I think we do want to > finalize a draft for public review by september, and it seems > very unfortunate not to have that device in the draft at all. > As I wrote in the other thread I'm fine either way. But I don't think I will be able to muster the time and go trough he spec and the code by September. I have a couple of weeks of vacation in August, but I intend to stay tuned. Given the whole situation, I have the feeling merging the thing even if it's a bit 'on risk' seems to be the most reasonable option. I often tend to regard standards as 'holy cow that is cast in stone'. That makes me over-cautious. If something needs to be fixed, we can fix it when the need becomes apparent. Best regards, Halil