Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Sponsors & Funding
Date: Thu, 02 Oct 2025 19:28:48 +0300
Message-ID: <2322583.iZASKD2KPV@basile.remlab.net> (raw)
In-Reply-To: <20251002125516.GF29660@pb2>

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. 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 money will be used for FFmpeg and the FFmpeg community. (Maintenance,
> Development, Infra, Testing, Travel, Research, ...)

I don't think that we need to vote on funding infra, travel and testing. Those 
things are already being funded through SPI regardless of this call for vote, 
and nobody suggested that that should stop.

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.

>     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.

-- 
德尼-库尔蒙‧雷米
Hagalund ny stad, f.d. Finska republik Nylands



_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-10-02 16:29 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 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-10-03 22:52   ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
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=2322583.iZASKD2KPV@basile.remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /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