From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] financial sustainability Plan A (SPI) Date: Fri, 27 Oct 2023 14:20:58 +0200 Message-ID: <20231027122058.GP3543730@pb2> (raw) In-Reply-To: <CAK+ULv7zTkzSFnmFDrh2A86xWsyFj3qVqHBghvhLsq8JKaZ73w@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2212 bytes --] On Thu, Oct 26, 2023 at 06:28:25PM -0700, Kieran Kunhya wrote: > Hi, > > On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel < > ffmpeg-devel@ffmpeg.org> wrote: > > > 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. > > > > Reimbursement requests for clearly defined things like travel costs with > receipts, or hardware that the project owns is in no way comparable to > consulting work, contracts, statements of work etc. And the current swscale > proposal is far from this too. [...] > Agreement via mailing list for money is a recipe for disaster. What we need > are clear statements of work that are voted on by TC. > We can't even agree on patch reviews, throwing money into the mix is > throwing gasoline into the fire. GSoC pays about 5000USD for each individual over the summer. The proposals for such projects where discussed and agreed upon with very little if any disagreement. We needed no formal votes, we needed no comittees and also for patches, you can pick out the 10 most controversal ones in a year and these are highly vissible, but there are thousands that are reviewed and applied by consensus with noone objecting. You seem to pick the most controversal things as reference, and argue that it cant work. 1 of a 100 patches got stuck in fights so 90 of 100 funding proposals would get stuck ? Now we still have no proposals for SPI money, but assume we do. either we all agree or theres someone who publically objects, in the later case we will first try to reach an agreement if that fails. We can vote, its not a big deal. 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: 251 bytes --] _______________________________________________ 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 12:21 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 [this message] 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=20231027122058.GP3543730@pb2 \ --to=michael@niedermayer.cc \ --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