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: Thu, 26 Oct 2023 21:41:41 +0200 Message-ID: <9dc06c51-3aa0-3b71-b0a6-12a5e4cfe662@mail.de> (raw) In-Reply-To: <CAK+ULv4Z9S8MLUZtw_-JK8E=q0eKpiQjDbQR25aWxeurRSi-vA@mail.gmail.com> Am 26.10.23 um 21:02 schrieb Kieran Kunhya: >> >> * 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. And once the community >> approves >> it and stefano with you double checks with SPI if we will be able to >> fund it. >> Then you can start working on it >> > > The mailing list is already an absolute disaster as it is and you now want > to put money into the mix? Of course. FFmpeg has a donations account. So the money is already there and already used for the reimbursement requests. Whatever we spent it for needs to be decided by the community. Spending more money instead of just watch it growing is a good thing. That this will lead to more "disaster" is an assumption without basis. Even if this does happen and fails, its still better than not having even tried. Also, you just advertised FFmpeg and asked for more financial support in your talk at Demuxed [1] - so I figure your prefered way of doing that would be to channel money into some company without the community being involved? And since you also advertised explicitly for FFlabs - what is your relation to FFlabs? I own 25% of that company and I am not aware of any relationship. You just did advertise FFlabs because... FFlabs exists? FFlabs is a company co-owned by some FFmpeg developers, it's not FFmpeg nor can it represent it or act on its behalf. As soon as we pay developers via SPI it can become a good zero-trust environment for donators to offer tasks & money to FFmpeg and handle the money flow via SPI. The donators can be sure that their issues are handled properly in the project (on the ML) and do not flow away into some other sink and the developers can be sure to get their money from SPI because the offer is public and backed by the FFmpeg SPI account. Sounds like a quite trustworthy and most importantyl transparent way to handle things and build up trust in potential donators that the money they spent actually end up with FFmpeg. > I don't think developers should be paid via SPI for this reason. I think supporting FFmpeg developers via SPI fits perfectly into what we have SPI for in the first place - an independant entity that handles the community funds with absolute objectivity and no intrinsic interest whatsoever. In contrast to any company, including (my own-ish) FFlabs. -Thilo [1] https://drive.google.com/file/d/1B9VoiT6sjW4vWWsp6ipudLz73QtdBbGi/view?usp=sharing _______________________________________________ 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-26 19:41 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 [this message] 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 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=9dc06c51-3aa0-3b71-b0a6-12a5e4cfe662@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