Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: code+AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@ffmpeg.org,
	Nicolas George <george@nsup.org>,
	Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: Soliciting sponsorship (was: WIP: avfilter: add Bungee audio stretch filter (PR #20697))
Date: Tue, 14 Oct 2025 11:53:52 +0100
Message-ID: <CABGuwE=zG56j+LH0KUrKfj+O+DdxCNYM4studTxMLm1_n+ca3A@mail.gmail.com> (raw)
In-Reply-To: <aO4moHccjc9akEP-@phare.normalesup.org>

On Tue, Oct 14, 2025 at 11:32 AM Nicolas George via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> michaelni (HE12025-10-13):
> > Also you would have to convince the community, that we want this. iam
> > not sure how the community would think about it, but for example you
> > could offer to donate a percentage of your profits from this to
> > ffmpeg.
>
> Hi. I procrastinated replying about soliciting sponsorships, but if it
> looks like that I cannot anymore. Also, it must not be discussed in the
> dark of an obscure pull request, it needs to be seen on the
> mailing-list.
>
> If this is how us soliciting sponsorships looks like, then we must
> absolutely not do it.
>
> “Pay us and we will consider ignoring the qualms we have about the
> licensing issues of your contribution” is already very bad by itself. It
> is even badder when we realize it is only one step from “pay us and we
> will consider ignoring the qualms we have about the poor quality of your
> code”.
>
> Ideally, accepting contributions should be judged on the merits of the
> contribution itself: is the code beautiful? does it bring practical
> benefit to our users? Out of necessity we have to add: will this be
> properly maintained? But no more.
>
> We can solicit sponsorship, sure, but even the appearance that the money
> is a tit-for-tat for getting one's code into the project, getting
> excellent publicity and future maintenance work for cheap, would be
> extremely detrimental.
>

I agree.
There's is definitely a discussion to be had about the reasons FFmpeg
accepts a third-party lib. There are now many libs being proposed into
FFmpeg as marketing exercises.

I also think we should encourage people to maintain and more
importantly test their own repositories of FFmpeg with their open
source or proprietary libs (on Forgejo?).

Regards,
Kieran Kunhya
_______________________________________________
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 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FFmpeg/FFmpeg/pulls/20697@code.ffmpeg.org>
     [not found] ` <reply-AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@code.ffmpeg.org>
     [not found]   ` <FFmpeg/FFmpeg/pulls/20697/comment/11972@code.ffmpeg.org>
2025-10-14 10:32     ` [FFmpeg-devel] " Nicolas George via ffmpeg-devel
2025-10-14 10:53       ` Kieran Kunhya via ffmpeg-devel [this message]
2025-10-14 11:39         ` [FFmpeg-devel] " Zhao Zhili via ffmpeg-devel
2025-10-14 12:22           ` Kieran Kunhya via ffmpeg-devel
2025-10-16  9:58             ` Nicolas George via ffmpeg-devel
2025-10-14 16:26       ` Michael Niedermayer via ffmpeg-devel
2025-10-14 17:02       ` Michael Niedermayer via ffmpeg-devel
2025-10-15 11:04       ` 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='CABGuwE=zG56j+LH0KUrKfj+O+DdxCNYM4studTxMLm1_n+ca3A@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code+AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@ffmpeg.org \
    --cc=george@nsup.org \
    --cc=kieran618@googlemail.com \
    /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