Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ga@ffmpeg.org, Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] [POLL][VOTE] Sponsors & Funding
Date: Thu, 2 Oct 2025 14:55:16 +0200
Message-ID: <20251002125516.GF29660@pb2> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2487 bytes --]

Hi all

As suggested in the thread with similar subject, here is the vote.
Please reply with a "Yes" or "No" to cast your vote.
Vote ends in 7 days. All members of the GA can vote


"Yes"
 - The FFmpeg project should actively seek sponsors and funding.
 - The money will be used for FFmpeg and the FFmpeg community. (Maintenance, Development, Infra, Testing, Travel, Research, ...)
 - The money would also be used to hire / employ / contract FFmpeg Contributors fulltime or whatever the preferrance of each Contributor is.
 - Work / employment shall be preferrentially be given to FFmpeg Developers / FFmpeg community members.
    This preferrance for "FFmpeg Developers / FFmpeg community members" shall be the only preferrance.
    Outside that preferrance, a fair selection process shall be used by the General Assembly which
    only maximizes FFmpegs future.
 - Goals are
    * to provide secure full time employment for every major FFmpeg contributor, who wants to have that.
    * to accelerate growth and improve quality
 - A fair selection process shall be used by the FFmpeg Community to select what the money is used for, which maximizes FFmpegs future.
 - The FFmpeg community will be the decission maker about these funds.
 - The FFmpeg community will, at any time be able to change the process of how these decission are made by public consensus.
 - In absence of privacy concerns, decissions will be made by public consensus amongth the commuity, or if that fails,
   public vote of the GA members requireing a 2/3 majority to release funds for some use.
 - For cases with privacy concerns, decissions will be made by consensus or (2/3 maj) vote amongth the General Assembly.
 - We will use SPI to collect the funds.
 - If significant limitations or obstacles occur with SPI then we will consider founding our own FFmpeg foundation.

"No"
 - leave things as they are


Some Notes:
    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.

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Give a rich man 100$ and he will turn it into 1000$.
Give a poor man 1000$ and he will spend it.

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

             reply	other threads:[~2025-10-02 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 12:55 Michael Niedermayer via ffmpeg-devel [this message]
2025-10-02 16:28 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-10-03 22:52   ` 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=20251002125516.GF29660@pb2 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ga@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