From: "Rémi Denis-Courmont" <remi@remlab.net> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [RFC] financial sustainability Plan A (SPI) Date: Fri, 27 Oct 2023 18:24:58 +0300 Message-ID: <4226268.VIldXYingC@basile.remlab.net> (raw) In-Reply-To: <8917ecab-84fc-8604-9dfd-36bb0bfeb1ea@mail.de> Hi, Le perjantaina 27. lokakuuta 2023, 15.24.38 EEST Thilo Borgmann via ffmpeg- devel a écrit : > >>> 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. This is about the funding organisation(s) and the recipient developer(s) in need of sustainable funding. While my income is public (if you know where to look), I sincerely doubt that many people *here* would want theirs published. I rather think that they would see it as a major intrusion to their privacy. I too prefer standard specifications and source code open, but this is about people's personal information, not source code. Whether you like it or not, that really is a *downside* of going through the mailing list or the GA, simply because it is a major turn-off. If SPI requires going through the mailing list, then that is also a downside of going through SPI. > > 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. But that has nothing to do with building a sustainable OSS development ecosystem. Funding small tasks is great to get students to work their summer on FFmpeg rather than writing proprietary business code at a local web company (at least if you have willing mentors). But Michael specifically framed this "financial sustainability plan" for grown- up adult "developers [who] no longer live with their parents". It is *not* sustainable to fund them with 5000€ bounties. At that point in our lives, most people would need somewhat stable income, both for financial and psychological well-being. If you have a credible plan for SPI to get enough income to provide that kind of stable income to even one developer, then by all mean, lets see that plan. But I don't see it. Offering bounties is a complete waste of time and money in this regard (it might be a good idea for other purposes, but that's a different discussion). > >>> 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. And I asked why it would be better to fund those hypothetical projects through SPI rather than privately and directly. -- レミ・デニ-クールモン http://www.remlab.net/ _______________________________________________ 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".
next prev parent reply other threads:[~2023-10-27 15:25 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 2023-10-27 15:24 ` Rémi Denis-Courmont [this message] 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=4226268.VIldXYingC@basile.remlab.net \ --to=remi@remlab.net \ --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