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] [RFC] FFlabs Sponsor Date: Fri, 10 Oct 2025 14:28:58 +0200 Message-ID: <aOj8CikyPPyis76s@neo> (raw) [-- Attachment #1.1: Type: text/plain, Size: 946 bytes --] Hi Everyone The FFmpeg community decided, that we should actively look for sponsors. And to do that, i will use my influence as shareholder of FFlabs to: Authorize the use of excess funds (that is funds FFlabs does not need for its own needs, obligations, benefit, growth, strategy, treasury), to be given to FFmpeg. Of course FFlabs needs to keep enough funds to ensure, it at no time, runs out of funds. Of course for this to be effective a single shareholders authorization is not enough. But if it becomes effective, then the FFmpeg community can choose to use these funds as it sees best fit for FFmpegs growth. I believe this is also closer to the vision, several shareholders had, of what FFlabs should be. Comments and Suggestion are welcome -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Nations do behave wisely once they have exhausted all other alternatives. -- Abba Eban [-- 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 reply other threads:[~2025-10-10 13:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-10-10 12:28 Michael Niedermayer via ffmpeg-devel [this message] 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 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=aOj8CikyPPyis76s@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