Re: [virtio-dev] Re: [RFC PATCH v6] virtio-video: Add virtio video device specification

[Alexander Gordeev <alexander.gordeev@opensynergy.com>]

On 17.05.23 18:28, Cornelia Huck wrote:
>>>> I also hope to be able to update virtio-video at a faster pace. Please
>>>> let me try.
>>>
>>> Please hold on a bit - there are two things here.
>>>
>>> 1) I'd like to settle the virtio-v4l2/virtio-video argument first to
>>> make sure we don't get two things clashing head-on. As far as codecs
>>> are concerned we certainly don't need both. Cornelia, I think we'll
>>> need you to make a call on this, or at least tell us what you need to
>>> make the call. If it helps I can send a draft of what the virtio-v4l2
>>> spec would look like, it should be relatively short.
>>>
>>> 2) I (and other ChromeOS contributors) have been driving this spec so
>>> far and while I think virtio-v4l2 is a better solution, I have not
>>> said I would give up on virtio-video if virtio-v4l2 was not adopted
>>> and will keep iterating on it in that case.
>>
>> It actually very much looks like you gave up. I mean, you developed it
>> for years, and now you'd like to throw it away. Well, I meant something
>> like "please have some faith in my ability to update virtio-video at a
>> faster pace". I think I already have the permission to continue the
>> development. You know, OpenSynergy also spent some time on the
>> virtio-video. This includes the draft v1 version and the V4L2 driver. I
>> think this was kind of an informal agreement between us, that you do the
>> spec and we do the driver. It didn't work well enough since draft v4, I
>> think. Now as our interests are not aligned anymore, it is fine to
>> continue separately. I'm not going to wait until you change your mind on
>> virtio-v4l2. Obviously you're very busy with it right now. If I stop and
>> wait now, we won't have the video device in the 1.3 release for sure. I
>> think when we are ready to develop virtio-video together again, we'll
>> need a better agreement.
>
> Please, can we just calm down here? This thread is painful to read
> already, and pointing at each other is not going to help us to come up
> with something that is generally agreeable. In the end, I want _a_ spec,
> and I don't really have a horse in V4L2 vs. video race, but having to
> dig through all of this in the hope of moderating things is just
> impossible if you're arguing in circles, and much of it seemingly being
> a rehashing about who said/did something or not.

I'm very sorry for all the noise. I think it is fine to reiterate the
arguments a couple times to make them more digestible. But then it is
sometimes hard to stop. Sorry for that.

Also I didn't want to show any disrespect to Alexandre and Keiichi. In
fact I have deep respect for what they have achieved: going from v1 with
lots of TBD placeholders to fairly complete v3 and then trying to
simplify things further. It just seems to me that few final steps are
missing. Also I very much like the idea of having a repository with all
the intermediate changes. This already helps increase transparency of
the spec development. I'd like to sort out licensing questions first and
then continue with the same thing. In the end it might be not relevant
anymore who exactly sends the patch to the mailing list.

I'd like to focus on the draft v7 and I'm also going to send it to this
mailing list (or to virtio-comments first) even though I totally
understand, that the decision is not made yet and that we may end up
throwing it all away. If the decision is made on June 30, it would be
better for everyone to have a spec, that is ready to be merged.

--
Alexander Gordeev
Senior Software Engineer

OpenSynergy GmbH
Rotherstr. 20, 10245 Berlin

Phone: +49 30 60 98 54 0 - 88
Fax: +49 (30) 60 98 54 0 - 99
EMail: alexander.gordeev@opensynergy.com

www.opensynergy.com

Handelsregister/Commercial Registry: Amtsgericht Charlottenburg, HRB 108616B
Geschäftsführer/Managing Director: Régis Adjamah

Please mind our privacy notice<https://www.opensynergy.com/datenschutzerklaerung/privacy-notice-for-business-partners-pursuant-to-article-13-of-the-general-data-protection-regulation-gdpr/> pursuant to Art. 13 GDPR. // Unsere Hinweise zum Datenschutz gem. Art. 13 DSGVO finden Sie hier.<https://www.opensynergy.com/de/datenschutzerklaerung/datenschutzhinweise-fuer-geschaeftspartner-gem-art-13-dsgvo/>

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org