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: Fri, 7 Nov 2025 15:00:05 +0100
Message-ID: <aQ37ZdYNdArB5MUl@phare.normalesup.org> (raw)
In-Reply-To: <82ed1487-f459-4d4c-9a48-cbfbf48ea266@rothenpieler.org>
Timo Rothenpieler via ffmpeg-devel (HE12025-11-06):
> Couldn't we simply have any design-discussions and decisions before the
> bounty is started, so the design becomes part of what the bounty is posted
> for?
Not really, I would say. To paragraph the famous saying “no battle plan
survives the first contact with the enemy”: no design plan survives the
first line of code.
It is by trying to implement the design you draw on your white board
that you realize it does not work. Or the other way around: while
implementing your realize there is a simpler, more elegant way to do it.
There is a back-and-forth between coding and 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-07 14:00 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
2025-11-06 14:51 ` Timo Rothenpieler via ffmpeg-devel
2025-11-07 14:00 ` Nicolas George via ffmpeg-devel [this message]
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=aQ37ZdYNdArB5MUl@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