Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [RFC] financial sustainability Plan A (SPI)
Date: Fri, 27 Oct 2023 14:24:38 +0200
Message-ID: <8917ecab-84fc-8604-9dfd-36bb0bfeb1ea@mail.de> (raw)
In-Reply-To: <BEEBC1E7-FE3B-42B0-BCD7-6670B659CA09@remlab.net>

Am 27.10.23 um 13:30 schrieb Rémi Denis-Courmont:
> Hi,
> 
> Le 27 octobre 2023 14:10:15 GMT+03:00, Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>>> Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>>>> This is financial sustainability Plan A (SPI)
>>>> ATM SPI has like 150k $, we do not activly seek donations, we do not currently
>>>> use SPI money to fund any development. SPI money is ultimately controlled by
>>>> the FFmpeg community and everything is transparent and public.
>>>
>>>> 1. We should fund some FFmpeg development with SPI-FFmpeg money
>>>
>>> Why should it be via SPI? What's the benefit of that hypothetical future additional funding going via SPI, as opposed to:
>>
>> obviously transparency and community control. None of which is given by the options you list.
> 
> Do you want transparency there? This is *not* about having open source code and the public code review. 

Yes, absolutely. We are an *open* project.
And no, we of course don't talk about the review part.


> This is about people's work commitments and compensation. Martin and I are about the only people here whose taxable income is public information. It doesn't seem to me that people typically want that sort of information public.

If s.o. is not fine with receiving these funds in public, than this is not our 
public money's problem. This cuts off this individual from receiving SPI money 
in the first place but not cutting anyone off the other options you listed.
We don't refund in private for travel & hardware, same must be true for SPI 
sponsored development.


> And then that means more non-technical work for the unpaid *other* members of the community in managing the paid developers' work. This is also unlikely to ve welcome to most.
> 
>>> - via FFlabs or any other reputable OSS multimedia consulting company,
>>> - a consortium of large companies, or
>>> - directly to a salaried or freelance developer.
>>
>> Also, it is not that these shall cease to be done. Using SPI money is one more option.
> 
> Using SPI money would hypothetically be an option if there was enough money. Currently there is not.

There is enough budget to fund several of the smaller tasks Michael proposed.


>>> That's the part that you'd need to clarify first. What relevant flashy cool development will attract those donations? Why should they be funded by donations rather than more traditional business transactions?
>>
>> Hen & egg.
> 
> What? Why do you need to start spending money before you can have ideas of cool projects? That makes zero sense to me.

What? Michael asked specifically to propose cool projects.


>>>> * If you have some flashy FFmpeg project you want to work on with a cost of
>>>>    between 5-15k $ then propose it on the mailing list, make yourself ready for
>>>>    some paperwork complexities and some public debate as thats the first time we
>>>>    try this, there will be extra issues likely.
>>>
>>> I don't think that code bounties count toward OSS "sustainability". It's condoning the so-called jig economy, which is the opposite, IMO.
>>
>> Code bounties sustain a/the developer(s) working on it and that way they stay active with the project.
> 
> No they don't. They make up a precarious insecure and unstable financial situation. That's the literal opposite of sustainability.
> 
> It's fine to take a bounty as a bit of extra income, or as an internship, but that is about it.

That might be true for you and not for others. You deleted history here where I 
said there are more reliable ways but they don't void bounties and that even if 
this thread is about bounties, we are not limited to them.

-Thilo
_______________________________________________
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-27 12:24 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 15:45 Michael Niedermayer
2023-10-26 19:02 ` Kieran Kunhya
2023-10-26 19:41   ` Thilo Borgmann via ffmpeg-devel
2023-10-27  1:28     ` Kieran Kunhya
2023-10-27 10:23       ` Thilo Borgmann via ffmpeg-devel
2023-10-27 13:38         ` Kieran Kunhya
2023-10-27 15:08           ` Thilo Borgmann via ffmpeg-devel
2023-10-27 15:38             ` Rémi Denis-Courmont
2023-10-27 12:20       ` Michael Niedermayer
2023-10-27 10:43 ` Rémi Denis-Courmont
2023-10-27 11:10   ` Thilo Borgmann via ffmpeg-devel
2023-10-27 11:30     ` Rémi Denis-Courmont
2023-10-27 12:24       ` Thilo Borgmann via ffmpeg-devel [this message]
2023-10-27 15:24         ` Rémi Denis-Courmont
2023-10-27 16:05           ` Michael Niedermayer
2023-10-27 16:14             ` Rémi Denis-Courmont
     [not found]               ` <AD4E0E39-49ED-4C96-8C12-9EAF6AFC00B0@cosmin.at>
2023-10-27 18:52                 ` Cosmin Stejerean via ffmpeg-devel
2023-10-27 19:00                   ` Rémi Denis-Courmont
     [not found]                     ` <5F5D6E6A-D85E-43E1-AF5B-B5CFBE60BF94@cosmin.at>
2023-10-27 19:04                       ` Cosmin Stejerean via ffmpeg-devel
2023-10-27 12:27     ` Michael Niedermayer
2023-10-27 12:32   ` Michael Niedermayer
2023-10-27 13:46     ` Kieran Kunhya
2023-10-27 15:08       ` Michael Niedermayer
2023-10-28 14:20 ` Ronald S. Bultje
2023-10-28 15:30   ` Thilo Borgmann via ffmpeg-devel
2023-10-28 16:43     ` Ronald S. Bultje
2023-10-28 17:21       ` Michael Niedermayer
2023-10-28 18:01         ` Michael Niedermayer
2023-10-28 18:58           ` Paul B Mahol
2023-10-28 20:46           ` Michael Niedermayer
2023-10-29 14:35           ` Rémi Denis-Courmont
2023-10-29 16:12             ` Michael Niedermayer
2023-10-29 16:22               ` Kieran Kunhya
2023-10-29 19:36               ` Rémi Denis-Courmont
2023-10-31 16:58                 ` Michael Niedermayer
2023-10-31 17:19                   ` Rémi Denis-Courmont
2023-10-31 17:31                     ` Michael Niedermayer
2023-10-31 17:37                       ` Hendrik Leppkes
2023-10-31 17:48                         ` Michael Niedermayer
2023-11-01  0:04                           ` Thilo Borgmann via ffmpeg-devel
2023-11-01  1:27                             ` Steven Liu
2023-10-29 16:47             ` Nicolas George
2023-10-29 19:43               ` Ronald S. Bultje
2023-10-29 19:46                 ` Nicolas George
2023-10-29 19:53                   ` Ronald S. Bultje
2023-10-29 20:10                   ` Paul B Mahol
2023-10-29 20:03               ` Rémi Denis-Courmont
2023-10-29 20:43                 ` Nicolas George
2023-10-28 21:17         ` Kieran Kunhya
2023-10-29 15:40           ` Michael Niedermayer
2023-10-28 17:21       ` Thilo Borgmann via ffmpeg-devel
2023-10-30  7:32 ` Gijs Peskens

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=8917ecab-84fc-8604-9dfd-36bb0bfeb1ea@mail.de \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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