[FFmpeg-devel] [PATCH] MAINTAINERS: Add Haihao Xiang for vaapi

Xiang, Haihao haihao.xiang at intel.com
Mon Dec 20 09:36:02 EET 2021


On Wed, 2021-12-15 at 15:32 +0100, Michael Niedermayer wrote:
> On Tue, Dec 14, 2021 at 10:31:40PM +0000, Soft Works wrote:
> > 
> > 
> > > -----Original Message-----
> > > From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of Michael
> > > Niedermayer
> > > Sent: Tuesday, December 14, 2021 10:40 PM
> > > To: FFmpeg development discussions and patches <ffmpeg-devel at ffmpeg.org>
> > > Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: Add Haihao Xiang for
> > > vaapi
> > > 
> > > On Tue, Dec 14, 2021 at 12:16:16PM -0800, Philip Langdale wrote:
> > > > On Tue, 14 Dec 2021 16:39:40 +0000
> > > > "Eoff, Ullysses A" <ullysses.a.eoff at intel.com> wrote:
> > > > 
> > > > > I have not seen any objections.
> > > > > I just added Mark to CC using their email found on this ML.
> > > > > Unfortunately, we don't have current email contact for
> > > > > Gwenole (whom has not worked on ffmpeg for ~6 years).
> > > > > Who else can make the approval, aside from the inactive people
> > > > > previously listed?
> > > > 
> > > > Are people reluctant to approve?
> > > 
> > > I dont think so, iam just extra carefull as someone on IRC noticed that
> > > "everyone and their grandmother who's worked for intel's got push access"
> > > 
> > > There where also some complaints about code quality/cleanlyness
> > > toward intels contributions
> > 
> > That's true. There are differences, and my expressed support is 
> > specifically tied to the person, not about having just "somebody".
> > 
> > I have my reservations about too early adoption of oneVPL and I think
> > the patchset "Cleanup QSV Filters.." is doing too many things at once,
> > but well - being a maintainer still doesn't mean that one could merge
> > anything without consent.
> > 
> > But the current situation, like having two or three people working full-time
> > on the subject being depending on somebody who isn't following progress
> > and unable assess, evaluate and test proposed changes is quite awkward.
> 
> yes
> 
> 
> > 
> > > So i just wanted to make sure there are no objections (iam not conciously
> > > aware of any objections to these MAINTAINER additions ATM)
> > > 
> > > 
> > > > I'll give it my approval to have on
> > > > the record. If the old maintainers want to emerge from the woodwork and
> > > > object after the fact, they are welcome to do so, but we can't just sit
> > > > around indefinitely. 
> > 
> > I'm actually wondering, whether registered maintainers that do not 
> > respond anymore to contributions for a certain amount of time,
> > shouldn't be unregistered automatically at some point?
> 
> If they never react they should be removed when a new volunteer is added.
> they should be informed about that when possible though.
> Also when there is noone else, then listing the last maintainer even if
> (s)he is mostly inactive still can make sense as it gives at least some point
> of contact 

Thanks all of you for your kink support. I'm glad to maintain vaapi plugin, 
will offer efforts to improve / enhance vaapi plugins and make it more useful to
vaapi user. I'd appreciate it if someone could make the approval and apply this
patch.

Thanks
Haihao




More information about the ffmpeg-devel mailing list