From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Thu, 6 Nov 2025 09:40:06 +0100
Message-ID: <aQxe5puEVg4JOWb9@phare.normalesup.org> (raw)
In-Reply-To: <C9686E44-E543-4D7C-9B13-58B9ACA524A9@remlab.net>
Rémi Denis-Courmont (HE12025-11-04):
> From a technical standpoint, that seems very agreeable indeed. But at
> the same time, it sounds unreasonable to expect that of a bounty
> claimant.
Can you elaborate why you think that? We set the rules.
> AFAICT, the only way to resolve that contradiction is to not have
> bounties for features that require design decisions at all. Otherwise
> problems like the one you claim of the channel layout API are just
> bound to repeat eventually.
>
> That's not to say that they can't be sponsored some way, but not the
> bounty way.
>
> In fact, I tend to be against bounties in general. At least that
> should not be the default model, IMO.
The channel layout API was not the result of a bounty, IIRC. AFAIK, we
do not know publicly how it was funded, or even if. We obviously have no
power to prevent somebody to work on a >100 patch series alone in their
free time, but unlike funded work there is no incentive to work alone.
I would agree with you to exclude things that require design from
bounties, but note that it would exclude the task discussed presently,
as “improve the filter negotiation around hardware filters” is mostly
design.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-06 8:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 2:40 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 19:16 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 20:35 ` Michael Niedermayer via ffmpeg-devel
2025-10-14 22:28 ` Timo Rothenpieler via ffmpeg-devel
2025-10-14 22:52 ` Michael Niedermayer via ffmpeg-devel
2025-10-15 4:39 ` Kieran Kunhya via ffmpeg-devel
2025-10-15 8:31 ` Nicolas George via ffmpeg-devel
2025-10-16 9:28 ` Kieran Kunhya via ffmpeg-devel
2025-10-16 11:20 ` Michael Niedermayer via ffmpeg-devel
2025-10-30 19:42 ` Nicolas George via ffmpeg-devel
2025-11-01 23:09 ` Michael Niedermayer via ffmpeg-devel
2025-11-18 19:40 ` Nicolas George via ffmpeg-devel
2025-10-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59 ` Michael Niedermayer via ffmpeg-devel
2025-11-01 23:38 ` Niklas Haas via ffmpeg-devel
2025-11-02 0:50 ` Timo Rothenpieler via ffmpeg-devel
2025-11-02 2:09 ` Michael Niedermayer via ffmpeg-devel
2025-11-03 17:44 ` Niklas Haas via ffmpeg-devel
2025-11-04 19:39 ` Nicolas George via ffmpeg-devel
2025-11-04 20:36 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-06 8:40 ` Nicolas George via ffmpeg-devel [this message]
2025-11-06 14:51 ` Timo Rothenpieler via ffmpeg-devel
2025-11-07 14:00 ` Nicolas George via ffmpeg-devel
2025-11-06 19:42 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-05 15:28 ` Lynne via ffmpeg-devel
2025-11-19 18:31 ` ff--- via ffmpeg-devel
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=aQxe5puEVg4JOWb9@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.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