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: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] [RFC] Funded Task Ideas
Date: Tue, 14 Oct 2025 04:40:06 +0200
Message-ID: <aO24BiJQWDvXqKFP@neo> (raw)


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

Hi Everyone

As we are now looking for sponsors, we also should look for tasks to fund.
I suggest, we first do some brainstorming and make a list, and then figure out which
tasks we want to sponsor (or maybe someone wants to do one as a volunteer)

Heres some random ideas from me /mostly things for which i am not able to find the time ATM
(that is, iam happy if someone else does these)
please add your ideas.

* cherry pick the remaining codecs and demuxers from almpeg
* cleanup new tickets on trac (aka close (invalid/needs more info/fixed) or open
* do something about the difference between mitre and our CVE list (that is go over the output from tools/compare-cvelists.sh)
* do we have any bugs or feature requests that have alot of votes on them ?

thx

PS: once we have enough yearly income we can look at hiring / funding people fulltime.

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Elect your leaders based on what they did after the last election, not
based on what they say before an election.


[-- 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-14  2:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  2:40 Michael Niedermayer via ffmpeg-devel [this message]
2025-10-14 19:16 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 20:35 ` Michael Niedermayer via ffmpeg-devel
2025-10-14 22:28 ` Timo Rothenpieler via ffmpeg-devel
2025-10-14 22:52   ` Michael Niedermayer via ffmpeg-devel
2025-10-15  4:39     ` Kieran Kunhya via ffmpeg-devel
2025-10-15  8:31       ` Nicolas George via ffmpeg-devel
2025-10-16  9:28         ` Kieran Kunhya via ffmpeg-devel
2025-10-16 11:20         ` Michael Niedermayer via ffmpeg-devel
2025-10-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59   ` Michael Niedermayer 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=aO24BiJQWDvXqKFP@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 https://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/ https://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