From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org Date: Sat, 26 Jul 2025 16:57:15 +0200 Message-ID: <20250726145715.GR29660@pb2> (raw) In-Reply-To: <20250724180512.00007b6a@hawaiiantel.net> [-- Attachment #1.1: Type: text/plain, Size: 3631 bytes --] Hi On Thu, Jul 24, 2025 at 06:05:12PM -1000, compn wrote: > On Wed, 23 Jul 2025 11:59:23 +0200, Michael Niedermayer wrote: > > > Hello Kieran > > > > On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel wrote: > > > > About 2. (IMHO) > > > > * The solution is to hire carl or someone else (or find a volunteer) > > > > to do this work. Changing the tracker will not fix this. > > > > > > > > FFlabs should have enough captial to hire carl for this. People should > > > > ask > > > > FFlabs to hire him and carl to accept to be hired for this work. > > > > > > > > > The commercial decisions of FFlabs are for its shareholders during its > > > internal meetings, not this mailing list. > > > > Thats a misunderstanding. > > > > Let me quote the president and CEO: > > > > "The company is just a way to finance the community to work on the same > > things as usual." > > > > and > > > > "To me, the company should be transparent to the project. It's just a way > > to funnel money to the community." > > > > hello, > > fflabs should have its use and goals documented on its [...] > does not sound like a community focused company at all. i agree and i raised that issue with the CEO yesterday and asked where I could send proposed changes. But he is quite busy so dont expect that he will look into this right away. About raising the issue of employing carl. I have raised that multiple times, and i remember none of the shareholders objecting. But it never happened. This may make more sense if you consider that to employ him, 3 things really need to happen at the same time 1. carl needs to want to work for FFlabs 2. It has to fit into the greater strategy of FFlabs 3. FFlabs needs to have sufficient funds. In the early days, FFlabs simply did not have the funds to employ more people And also needed to concentrate on growth that is on people directly doing consulting work that brings in more money and customers Funds are available now AFAIK, but carl is no longer here Keep in mind 3 people quit in 2025 and revenue keeps growing so we should have funds to contract or employ more people. But there is of course also more work that needs to be done. And the promise our CEO gave to the community was to finance the community. So i think it does make sense that the community monitors it and if needed politely reminds and insists on adjustments ... Also if noone from the FFmpeg community wants to do any contract work or be employed by FFlabs in 2025. People need to understand that FFlabs is a "for profit" company and it cannot accumulate captial without paying taxes. So it would be wastefull, and FFlabs will likely use the captial for other things this year and it will just be lost for the FFmpeg community. In summary i think it does make sense for the FFmpeg community to think about where money could help teh most and then propose this to FFlabs as a clear and executable suggestion. PS: of course all funds available in FFlabs should be used in a way that grows FFmpeg and FFlabs. More money in FFlabs means more money available to the FFmpeg community. Thats why spending money in a way that brings in more money should be prioritized as long as we dont have enough to fund everything in FFmpeg that we want to fund. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No human being will ever know the Truth, for even if they happen to say it by chance, they would not even known they had done so. -- Xenophanes [-- 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:[~2025-07-26 14:57 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-22 3:53 Lynne 2025-07-22 8:44 ` Kacper Michajlow 2025-07-22 9:15 ` Jacob Lifshay 2025-07-25 3:40 ` compn 2025-07-25 3:58 ` Jacob Lifshay 2025-07-25 4:36 ` compn 2025-07-25 11:41 ` Nicolas George 2025-07-25 14:20 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 4:05 ` Lynne 2025-07-22 15:01 ` Leo Izen 2025-07-23 4:01 ` Lynne 2025-07-22 23:04 ` Michael Niedermayer 2025-07-23 4:01 ` Lynne 2025-07-23 9:16 ` Michael Niedermayer 2025-07-23 9:39 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 9:59 ` Michael Niedermayer 2025-07-23 10:02 ` Kieran Kunhya via ffmpeg-devel 2025-07-23 11:48 ` Nicolas George 2025-07-25 4:05 ` compn 2025-07-26 14:57 ` Michael Niedermayer [this message] 2025-07-23 9:38 ` Michael Niedermayer 2025-07-23 11:49 ` Nicolas George 2025-07-26 17:03 ` Derek Buitenhuis 2025-07-26 19:29 ` Timo Rothenpieler 2025-07-26 20:01 ` Derek Buitenhuis 2025-07-26 20:14 ` Timo Rothenpieler 2025-07-26 20:24 ` Kacper Michajlow 2025-07-26 20:29 ` Derek Buitenhuis 2025-07-26 20:41 ` Timo Rothenpieler 2025-07-26 20:45 ` Derek Buitenhuis 2025-07-26 21:07 ` Kacper Michajlow 2025-07-26 21:18 ` Timo Rothenpieler 2025-07-26 22:44 ` Michael Niedermayer 2025-07-26 22:57 ` Timo Rothenpieler 2025-07-26 22:48 ` Michael Niedermayer 2025-07-26 20:28 ` Derek Buitenhuis 2025-07-26 20:14 ` Kacper Michajlow 2025-07-26 20:23 ` Timo Rothenpieler 2025-07-26 20:29 ` Kacper Michajlow 2025-07-26 20:33 ` Derek Buitenhuis
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=20250726145715.GR29660@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