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: [POLL][VOTE] Sponsors & Funding Date: Sat, 4 Oct 2025 00:52:22 +0200 Message-ID: <aOBTpoOj_oqQYSTN@neo> (raw) In-Reply-To: <2322583.iZASKD2KPV@basile.remlab.net> [-- Attachment #1.1: Type: text/plain, Size: 4168 bytes --] Hi Remi On Thu, Oct 02, 2025 at 07:28:48PM +0300, Rémi Denis-Courmont via ffmpeg-devel wrote: > Le torstaina 2. lokakuuta 2025, 15.55.16 Itä-Euroopan kesäaika Michael > Niedermayer via ffmpeg-devel a écrit : > > "Yes" > > - The FFmpeg project should actively seek sponsors and funding. > > Repeating myself but that sentence does not mean anything. How are we supposed > to vote on something so vague? > > If FFmpeg is/becomes a legal entity of its, that sort of mission statement > could be included in the statutes. That could justify an FFmpeg foundation > funding trusted community members to attend tradeshows to look for sponsors > and funding, for example. But that sentence cannot be thrown like this on its > lonesome. Otherwise, FFmpeg is just a collection of assets such as trademarks, > domain names and hardware held by SPI or Fabrice. Assets can't "actively seek > sponsors". > > I suppose that you mean the FFmpeg community. yes > But as Gyan already pointed out > in previous threads, even that's poorly defined. And in any case, One Does Not > Simply compel the community to "actively seek sponsors". People can actively > seek sponsors already, and they can also choose not to. Voting one way or the > other will make no differences. The intend here is more, to decide on the direction. Do we, as a team, want to actively look for sponsors or not ? Without this direction, its very hard for one person to talk to sponsors, while another publically maybe says, "FFmpeg does not look for sponsors". Its to establish a common direction. > > > - The money will be used for FFmpeg and the FFmpeg community. (Maintenance, > > Development, Infra, Testing, Travel, Research, ...) [...] > > As for research, bluntly, this is too vague and open-ended. Normally research > has deliverables such as peer-reviewed papers or working code or whatever. > Also this is probably better handled via academia or via NLnet-type > foundations. Each individual use of money, would be agreed by consensus or 2/3 majority. But we need a list, that we can show to sponsors, so they understand what they are paying for. > > > Employing people is complex as it requires compliance to local > > regulations. Thus it should be expected that for employing developers, we > > will likely need to work together with local companies. That is if we want > > to employ someone in Country X we could partner with a company in Country X > > which then employs the developer and SPI would pay that company. > > True. But with that in mind, what's the difference between the "yes" and "no" > options? Developers can already be hired by local companies or run their own > consultancies. I believe some people here are already doing just that. I think, i have failed to explain this clearly. One can go to bigcorp and ask them to donate 100k per year to FFmpeg/SPI, but with: "Yes" We can say, that this extra money will be used to hire people, and for maintaince and development. A Company that depends on FFmpeg has a reason to spend 100k/y here, its tiny for many companies, and they make MUCH larger sums with their buisness depending on FFmpeg. "No" Here we can just say, that we have used SPI money for travel and infra. And that SPI has been the intermediary of STF and GSoC for us. But we do not yet know what the additional money will be used for. I dont think many companies will agree to give us 100k/ year with such statement. This vote would give a clear direction, which we can present to potential sponsors. So maybe the vote could be summarized in Do we want to * hire people * pay for increased maintaince and development beyond the current capacity If yes, we need to look for sponsors, if no, we cannot really look for sponsors. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Homeopathy is like voting while filling the ballot out with transparent ink. Sometimes the outcome one wanted occurs. Rarely its worse than filling out a ballot properly. [-- 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-03 22:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-10-02 12:55 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-10-02 16:28 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel 2025-10-03 22:52 ` Michael Niedermayer via ffmpeg-devel [this message] 2025-10-03 23:09 ` Kieran Kunhya via ffmpeg-devel 2025-10-05 22:10 ` Michael Niedermayer via ffmpeg-devel 2025-10-09 15:00 ` Michael Niedermayer via ffmpeg-devel 2025-10-10 14:08 ` Kieran Kunhya 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=aOBTpoOj_oqQYSTN@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