From: "Xiang, Haihao" <haihao.xiang@intel.com>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: Add Haihao Xiang for vaapi
Date: Mon, 20 Dec 2021 07:36:02 +0000
Message-ID: <88ce05c8d24b4e4b8074a93e84c1b69c7b6cbb9d.camel@intel.com> (raw)
In-Reply-To: <20211215143217.GT2829255@pb2>
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@ffmpeg.org> On Behalf Of Michael
> > > Niedermayer
> > > Sent: Tuesday, December 14, 2021 10:40 PM
> > > To: FFmpeg development discussions and patches <ffmpeg-devel@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@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
_______________________________________________
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".
next prev parent reply other threads:[~2021-12-20 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211214040806.178814-1-ullysses.a.eoff@intel.com>
[not found] ` <DM8P223MB03657C6FA04CB6AE076AA183BA759@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
[not found] ` <DM6PR11MB27461D1A3846EF6326D7BE48BE759@DM6PR11MB2746.namprd11.prod.outlook.com>
[not found] ` <20211214163026.GO2829255@pb2>
[not found] ` <DM6PR11MB274670A384F4AC60F4244320BE759@DM6PR11MB2746.namprd11.prod.outlook.com>
[not found] ` <20211214121616.499620bf@fido6>
[not found] ` <20211214214010.GQ2829255@pb2>
[not found] ` <DM8P223MB03653A18ED636BAA80B0B7DDBA759@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
2021-12-15 14:32 ` Michael Niedermayer
2021-12-20 7:36 ` Xiang, Haihao [this message]
2021-12-20 22:33 ` Philip Langdale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88ce05c8d24b4e4b8074a93e84c1b69c7b6cbb9d.camel@intel.com \
--to=haihao.xiang@intel.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git