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 17:08:29 +0200 Message-ID: <20231027150829.GS3543730@pb2> (raw) In-Reply-To: <CAK+ULv44ORv76kMAK6aYeQ5iNgXCGGAiFJ6i-S2QZuqg22pxng@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2781 bytes --] On Fri, Oct 27, 2023 at 06:46:42AM -0700, Kieran Kunhya wrote: > On Fri, 27 Oct 2023 at 05:32, Michael Niedermayer <michael@niedermayer.cc> > wrote: > > > On Fri, Oct 27, 2023 at 01:43:34PM +0300, Rémi Denis-Courmont wrote: > > > > > > > > > Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer < > > michael@niedermayer.cc> a écrit : > > [...] > > > >* 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. > > > > This is just a first step. > > If we can attract the financial resources to pay people in a repeated > > fashion > > "each month" then thats absolutely what id like to do with SPI > > > > The thing we need for "sustainability" is someone to work full-time on > maintenance work yes, I think we all know and agree on that > like YUVJ removal iam not sure thats a good example, but anyway > that doesn't get done otherwise yes > (literally we have talked about this for the last five or more years). And thats great, but you know "talk" isnt good enough > Nor > would any company fund it as a bounty as it provides no benefit to them. now ive seen contracts and such but there are NDAs so i cannot give anything specific but this is wrong. Companies do care and fund some things that do not give an immedeate benefit to them but are rather things for the long term of the project (which will beneift the company only over time) > This is the complete opposite of "some flashy FFmpeg project". yes, let me spell my plan out again (which is bassed in fact on previous suggestions from others) 1. fund some flashy FFmpeg projects 2. seek more donations (explain its for sustainability and full time payments if possible and smaller but important areas (flashy projects) when its not enough for full time payments) do 1+2 in parallel, 1. helps 2. 3. if we manage to receive a steady stream of donations that can support part time or full time development, use it for that. The flashy stuff is to get started, we cannot pay people full time with a one time budget of 150k$. we can pay several people with that if we can get that in donations per year. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Asymptotically faster algorithms should always be preferred if you have asymptotical amounts of data [-- 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 15:08 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 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 [this message] 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=20231027150829.GS3543730@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