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

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
> Sent: wtorek, 14 lutego 2023 19:01
> 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
> 
> Feb 14, 2023, 13:10 by d.kozinski@samsung.com:
> 
> >
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Lynne
> > Sent: poniedziałek, 13 lutego 2023 18:32
> > 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
> >
> > Feb 13, 2023, 10:29 by d.kozinski@samsung.com:
> >
> >> Lynne, if it concerns us, we will comply with both the current and
> >> the new maintainership policy once your patchset is pushed. We see
> >> that your change has not yet been pushed into the main branch, and it
> >> appears that the discussion on this topic may still be ongoing,
> >> although both Michael and other maintainers have reviewed and
> >> commented on
> >>
> > it.
> >
> >>
> >>
> >
> > What do you mean both current and new policy?
> >
> > Lynne, you mentioned a new policy change on maintainership in one of
> > the previous emails:
> > "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."
> >
> 
> Fair enough, I'll just review the patchset while ignoring this patch.

Dear Lynne,

I just wanted to timidly remind you that we are still waiting for a review of our code.
Please have mercy on us and don't let us wait for ages. We don't want to wait indefinitely, and we would like to move forward with our project.

We understand that our patch is not a tiny piece of code, and we know the effort required to review it thoroughly is expected to be rather big. However, we would like to receive some feedback, even if it is just to let us know that currently you are overwhelmed by something else but you still keep it in your mind, and you will review it as soon as you are able. 
It is a little bit frustrating to wait for weeks without any feedback. Please, try to understand us.

We understand that there may be some issues that need to be addressed, and we are willing to work with you to fix any problems and ensure that our code meets all the requirements of the FFmpeg project. 
If there is something that requires improvement, please let us know so that we can address them.

On the other hand, if our code is already satisfactory, we would like to see it included in the FFmpeg repository. We believe that our patches could benefit the FFmpeg community, and we would like to contribute to the project. 
We appreciate your time and effort, and we look forward to hearing back from you soon.

Best regards,
DK
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://protect2.fireeye.com/v1/url?k=c6da1d34-a6388069-c6db967b-
> 000babd9f1ba-f1087034b8a00e05&q=1&e=f6840520-ddf5-4d1d-890b-
> 9f658856ac36&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmp
> eg-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".