Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files

["Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>]

Michael, could you review Lynne's policy change on maintainership?
It's essential for us to move EVC case one step forward.


-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
Sent: poniedziałek, 30 stycznia 2023 00:18
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in
Changelog and MAINTAINERS files

Jan 29, 2023, 10:57 by michael@niedermayer.cc:

> Hi
>
> On Fri, Jan 27, 2023 at 01:03:00PM +0100, Dawid Kozinski/Multimedia (PLT)
/SRPOL/Staff Engineer/Samsung Electronics wrote:
>
>> Hi,
>> It's been almost a month since we submitted our latest changes to the
FFmpeg patchwork. I know that EVC implementation isn't the only thing you
are working on at the moment but we'd like to do another step forward,
toward merging our implementation into the master branch of the FFmpeg
repository. 
>> The contribution is something that we take seriously so we'd like to
finally do some progress.
>> We would like to merge it as soon as it is enough good and it meets the
expected quality. Continual synchronization of our changes with the latest
FFmpeg changes and splitting our changes into patches is, let's say a
painstaking job. It would be much easier to develop and refine the code if
we could skip that hard splitting on patches step that we have to do each
time we do any, even small change.
>> We know that the new FFmpeg version will be released soon and you may be
absorbed and overwhelmed with the work related to the new release. However,
we'd be grateful if you found a little time and take a look at our latest
changes.
>> Last but not least. Do you have any plans related to including such
changes as our EVC implementation in the next release?
>>
>
> I cannot speak for others but ATM for me its difficult to add this 
> patchset to my todo list. If someone reviews and applies it it could 
> make it in for the release but will anyone, i do not know.
> What i can say is that if a patch which adds you to MAINTAINERS is 
> applied ping me and ill give you git write (unless there are some new 
> standing objections), and once you have that you can work on this code
with less pain.
> But i will leave applying the MAINTAINERS change to others too as some 
> people seemed not happy anout it and i think in such case its better 
> if a 2nd developer does that
>
> PS: Maybe you can troll the people who didnt like your MAINTAINERS 
> addition into reviewing & applying your patchset. Its not an 
> unreasonable request because if you dont have git write someone else 
> has to apply changes
>

I assign myself to personally review the patchset and push it, if you review
my policy change on maintainership. As I said, I have no objection on who
gets maintainership, just that it is done explicitly via a separate list in
the maintainers file.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org
with subject "unsubscribe".


_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".