Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Thu, 16 Oct 2025 13:59:37 +0200
Message-ID: <aPDeKbTKoZptFqU-@neo> (raw)
In-Reply-To: <aO-1aOM19ySVmewU@phare.normalesup.org>


[-- Attachment #1.1: Type: text/plain, Size: 3316 bytes --]

Hi Nicolas

On Wed, Oct 15, 2025 at 04:53:28PM +0200, Nicolas George via ffmpeg-devel wrote:
> Michael Niedermayer via ffmpeg-devel (HE12025-10-14):
> > As we are now looking for sponsors, we also should look for tasks to fund.
> 
> > PS: once we have enough yearly income we can look at hiring / funding
> > people fulltime.
> 
> I will step into it:
> 
> This is severely misguided.
> 
> FFmpeg is a Libre Software project: its goal is to make beautiful and/or
> useful software.
> 
> FFmpeg's goal is NOT to gain market shares.
> 
> FFmpeg's goal is NOT to turn a profit.
> 
> FFmpeg's goal is ABSOLUTELY NOT to get a livelihood for its authors.
> 

> The problem with people getting paid to work on FFmpeg is that it is a
> misaligned incentive. It creates the incentive to push the code as is
> instead of polishing it, instead of accepting suggestions to make it
> better. It creates the incentive to work alone rather than seek the
> insights of our peers.

I think you see only one possible way of doing this.
But really there are MANY ways

For example, one can pay for maintaince, for fixing issues.
One can pay developers and leave it up to them what to work on.

Just imagine for a moment we had 1M$ income per year in SPI or a ffmpeg foundation
we could pay 10+ developers fulltime and still leave it completely to them
what they work on.
There is no incentive to do things quick and ugly.


> 
> I am sure some developers are able to resist the incentive and not let
> the fact that they are paid for it reduce the quality of their code in
> favor of speed at all. But I am also sure they are not a majority.

From what iam reading on the subject of code quality and people, in general
developers care about code quality (also in commersial settings) this can
be a matter of pride and such stuff. Noone wants "their" code to be ugly
while management and also customers may push for "quick"

Of course if the developer doing the work is not competent the code will
show it but thats not "because its funded", its "because the developer had
a bad teacher or no teacher", or maybe because he wasnt given enough time

Also the real goal of funding, which i think people miss is to
facilitate that people can work on teh code.

That is very few can work fulltime on FFmpeg because, they need to pay rent
for their appartment, pay food, taxes, ... bascially the cost of living isnt 0

Funding a developer, be that as a contractor or emplyoee, is to allow him/her
to work more on FFmpeg.

You can also see it as,
* you pick people who want to work fulltime on FFmpeg and who have demonstrated
  previously they can and produce good code (or whatever other contribution they did) and ...
* then get them funded so they can work fulltime on FFmpeg

Theres no incentive here to produce bad code.

Also theres in fact often incentives to produce better code.
If you hire a contractor for a specific coding job. And the code she
produces is bad quality. Will you hire her again ?
No, so thats an incentive to produce good quality

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you think the mosad wants you dead since a long time then you are either
wrong or dead since a long time.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-10-16 12:00 UTC|newest]

Thread overview: 11+ 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-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59   ` Michael Niedermayer 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=aPDeKbTKoZptFqU-@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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