Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Nicolas George" <george@nsup.org>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Tue, 04 Nov 2025 22:36:04 +0200
Message-ID: <C9686E44-E543-4D7C-9B13-58B9ACA524A9@remlab.net> (raw)
In-Reply-To: <aQpWhVgQI66mHtdq@phare.normalesup.org>

Hi,

Le 4 novembre 2025 21:39:49 GMT+02:00, Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>Niklas Haas via ffmpeg-devel (HE12025-11-03):
>> 4. Developers should announce when they begin working on a bounty, and then
>>    nobody else should be able to claim it until a reasonable amount of
>>    time has passed. (Perhaps 12 weeks)
>
>I think we should add:
>
>5. When a bounty involves design decisions, these decisions must be
>   discussed on the mailing list before investing time and effort in
>   implementation.

From a technical standpoint, that seems very agreeable indeed. But at the same time, it sounds unreasonable to expect that of a bounty claimant.

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.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-11-04 20:38 UTC|newest]

Thread overview: 19+ 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-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 [this message]

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=C9686E44-E543-4D7C-9B13-58B9ACA524A9@remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=george@nsup.org \
    --cc=remi@remlab.net \
    /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