From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Michael Niedermayer <michael@niedermayer.cc> Subject: [FFmpeg-devel] Re: [RFC] FFlabs Sponsor Date: Fri, 10 Oct 2025 16:23:57 +0200 Message-ID: <aOkW_XNVLlMAmAXd@neo> (raw) In-Reply-To: <CAHGibzH02fN7AkYuA8CRZ1wa5jqjbv8bdo1f4c3bEiGa7+LAWQ@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --] Hi Devin On Fri, Oct 10, 2025 at 10:07:16AM -0400, Devin Heitmueller via ffmpeg-devel wrote: > On Fri, Oct 10, 2025 at 10:03 AM Kieran Kunhya via ffmpeg-devel > <ffmpeg-devel@ffmpeg.org> wrote: > > Posts about the business operations of FFlabs, a private company, are > > off-topic on this mailing list. > > > > Kieran > > Yeah, this seems like a really weird thing to declare in this forum. > If the question is whether the ffmpeg community would accept money > donated by fflabs? Of course. ok > But whether FFLabs decides to > contribute money to the community is really a discussion to be had > with your other shareholders. yes I think you misunderstand slightly. First, if i propose as a shareholder of FFlabs, to have some funds moved from FFlabs to FFmpeg. It makes sense to me, to ask the FFmpeg community first. Because iam not that smart. Someone might have a good suggestion which i can include in what i intend to propose to the other shareholders. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 163 bytes --] _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-10 14:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-10-10 12:28 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-10-10 14:02 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel 2025-10-10 14:07 ` Devin Heitmueller via ffmpeg-devel 2025-10-10 14:23 ` Michael Niedermayer via ffmpeg-devel [this message] 2025-10-10 14:33 ` Kieran Kunhya via ffmpeg-devel 2025-10-10 14:36 ` Nicolas George via ffmpeg-devel 2025-10-10 14:48 ` Kieran Kunhya via ffmpeg-devel 2025-10-11 9:19 ` Rémi Denis-Courmont via ffmpeg-devel
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=aOkW_XNVLlMAmAXd@neo \ --to=ffmpeg-devel@ffmpeg.org \ --cc=michael@niedermayer.cc \ /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 http://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/ http://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