Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] SWS cleanup / SPI Funding Suggestion
Date: Thu, 19 Oct 2023 00:12:27 +0200
Message-ID: <ZTBYSzAkNEiag6Ph@mariano> (raw)
In-Reply-To: <22048782.EfDdHjke4D@basile.remlab.net>

On date Wednesday 2023-10-18 19:30:11 +0300, Rémi Denis-Courmont wrote:
> Le keskiviikkona 18. lokakuuta 2023, 0.57.45 EEST Michael Niedermayer a écrit 
> :
> > On Tue, Oct 17, 2023 at 09:50:41PM +0300, Rémi Denis-Courmont wrote:
[...]
> > > What happens if more than one credible developer wants to take up the
> > > project?
> > 
> > Then 15k$ was too much
>
> So that's lowest bidder paradigm. Then you have to have a SoW first. See above.

This is similar to some of the issues with the GSOC program, the same
amount of money can mean something very different depending on the
contributors country/cost of life. So it is not really possible to
make a fixed price which is fair to everyone. Possibly it should be
computed depending on the country of the candidate developer depending
on some economic parameter.

> (...)
> > Whats the worst that can happen ?
> 
> The project fails because the terms were too vaguely defined. The GA become 
> even more reluctant to spend what little money FFmpeg has. Developers are 
> turned off from applying for sponsorship from FFmpeg. The contracted developer 
> rage-quits.

I can see this happening, but we cannot really predict without trying
- and we can learn from failure.

Another option would be to have something similar to bounties
(e.g. 100$ for each bug fixed - at least this might get low-hanging
fruits go away easily).

Or with some more organization we migth have the equivalent of FFSOC -
although this would be much more complicated to setup (since you have
to check with the student status and get the economical part straight,
deal with drops-out and so on).
_______________________________________________
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".

      reply	other threads:[~2023-10-18 22:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 19:19 Michael Niedermayer
2023-10-13 20:30 ` Vittorio Giovara
2023-10-13 21:23   ` Lynne
2023-10-13 22:02   ` Michael Niedermayer
2023-10-13 22:34 ` Niklas Haas
2023-10-13 22:42   ` James Almer
2023-10-13 22:54     ` Niklas Haas
2023-10-13 23:00       ` Vittorio Giovara
     [not found]         ` <8A960BE2-8364-4AF8-A9B5-E0551C19F9DF@cosmin.at>
2023-10-13 23:16           ` Cosmin Stejerean via ffmpeg-devel
2023-10-14 14:19             ` Kieran Kunhya
2023-10-14 17:00               ` Michael Niedermayer
2023-10-14 17:24                 ` Niklas Haas
2023-10-15 14:36                   ` Michael Niedermayer
2023-10-14 17:41                 ` Kieran Kunhya
2023-10-14 19:38                 ` Vittorio Giovara
2023-10-14 17:26               ` Anton Khirnov
2023-10-14 15:45             ` Michael Niedermayer
2023-10-14 17:53 ` Stefano Sabatini
2023-10-17 14:36   ` Michael Niedermayer
     [not found]     ` <430D0C5B-53A8-4920-B99A-D8BAD816D715@cosmin.at>
2023-10-17 16:58       ` Cosmin Stejerean via ffmpeg-devel
2023-10-18 21:53         ` Stefano Sabatini
2023-10-17 18:33   ` James Almer
2023-10-17 18:50 ` Rémi Denis-Courmont
2023-10-17 21:57   ` Michael Niedermayer
2023-10-17 22:10     ` Michael Niedermayer
2023-10-18 16:30     ` Rémi Denis-Courmont
2023-10-18 22:12       ` Stefano Sabatini [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=ZTBYSzAkNEiag6Ph@mariano \
    --to=stefasab@gmail.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