Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] [RFC] sponsors page
@ 2025-10-30  1:48 Michael Niedermayer via ffmpeg-devel
  2025-10-30  7:28 ` [FFmpeg-devel] " Steven Liu via ffmpeg-devel
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Niedermayer via ffmpeg-devel @ 2025-10-30  1:48 UTC (permalink / raw)
  To: FFmpeg development discussions and patches; +Cc: Michael Niedermayer


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

Hi all

i was talking with a company, who wants to sponsor FFmpeg
they asked if they would be listed in the GitHub readme.

I think we should instead add a sponsors.md and link to forgejo of it (forgejo can render .md)
or
instead put a sponsors.html on our webpage
similar to https://www.python.org/psf/sponsors/

the later would be release independant

what do people prefer ?

should we create that page with the first sponsor or wait until there are
multiple sponsors before creating the page ?

(Its plausible the first sponsors will be less well known companies)

should listing on that page be conditional on some sponsor level ?
or just all levels in order

Our levels: https://dir.floss.fund/view/funding/@ffmpeg.org (stolen from python)

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Some Animals are More Equal Than Others. - George Orwell's book Animal Farm

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [FFmpeg-devel] Re: [RFC] sponsors page
  2025-10-30  1:48 [FFmpeg-devel] [RFC] sponsors page Michael Niedermayer via ffmpeg-devel
@ 2025-10-30  7:28 ` Steven Liu via ffmpeg-devel
  2025-10-31  2:15   ` Michael Niedermayer via ffmpeg-devel
  0 siblings, 1 reply; 3+ messages in thread
From: Steven Liu via ffmpeg-devel @ 2025-10-30  7:28 UTC (permalink / raw)
  To: FFmpeg development discussions and patches
  Cc: Michael Niedermayer, Steven Liu

Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
于2025年10月30日周四 09:48写道:
>
> Hi all
>
> i was talking with a company, who wants to sponsor FFmpeg
> they asked if they would be listed in the GitHub readme.

I suggest we create a dedicated sponsor page.
As part of this, we should also define a more meaningful order for the list,
as sorting solely by year may not be the most effective approach.

>
> I think we should instead add a sponsors.md and link to forgejo of it (forgejo can render .md)
> or
> instead put a sponsors.html on our webpage
> similar to https://www.python.org/psf/sponsors/
>
> the later would be release independant
>
> what do people prefer ?
>
> should we create that page with the first sponsor or wait until there are
> multiple sponsors before creating the page ?
>
> (Its plausible the first sponsors will be less well known companies)
>
> should listing on that page be conditional on some sponsor level ?
> or just all levels in order
>
> Our levels: https://dir.floss.fund/view/funding/@ffmpeg.org (stolen from python)
>
> thx
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Some Animals are More Equal Than Others. - George Orwell's book Animal Farm
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [FFmpeg-devel] Re: [RFC] sponsors page
  2025-10-30  7:28 ` [FFmpeg-devel] " Steven Liu via ffmpeg-devel
@ 2025-10-31  2:15   ` Michael Niedermayer via ffmpeg-devel
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Niedermayer via ffmpeg-devel @ 2025-10-31  2:15 UTC (permalink / raw)
  To: FFmpeg development discussions and patches; +Cc: Michael Niedermayer


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

Hi Steven

On Thu, Oct 30, 2025 at 03:28:40PM +0800, Steven Liu via ffmpeg-devel wrote:
> Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
> 于2025年10月30日周四 09:48写道:
> >
> > Hi all
> >
> > i was talking with a company, who wants to sponsor FFmpeg
> > they asked if they would be listed in the GitHub readme.
> 
> I suggest we create a dedicated sponsor page.

ok


> As part of this, we should also define a more meaningful order for the list,
> as sorting solely by year may not be the most effective approach.

https://www.python.org/psf/sponsors/   sorts by the amount the sponsors contribute

I intend to use the same sorting, same terms and same values

Visionary Sponsor       USD 155000	Yearly
Sustainability Sponsor  USD 95000	Yearly
Maintaining Sponsor     USD 63000	Yearly
Contributing Sponsor    USD 33000	Yearly
Supporting Sponsor      USD 16500	Yearly
Partner Sponsor         USD 11000	Yearly
Participating Sponsor   USD 4000	Yearly
Associate Sponsor       USD 1500	Yearly

we already list these here:
https://dir.floss.fund/view/funding/@ffmpeg.org

thx

> 
> >
> > I think we should instead add a sponsors.md and link to forgejo of it (forgejo can render .md)
> > or
> > instead put a sponsors.html on our webpage
> > similar to https://www.python.org/psf/sponsors/
> >
> > the later would be release independant
> >
> > what do people prefer ?
> >
> > should we create that page with the first sponsor or wait until there are
> > multiple sponsors before creating the page ?
> >
> > (Its plausible the first sponsors will be less well known companies)
> >
> > should listing on that page be conditional on some sponsor level ?
> > or just all levels in order
> >
> > Our levels: https://dir.floss.fund/view/funding/@ffmpeg.org (stolen from python)
> >
> > thx
> >
> > --
> > Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> >
> > Some Animals are More Equal Than Others. - George Orwell's book Animal Farm
> > _______________________________________________
> > ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> > To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
> 
> Thanks
> Steven
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

z(9) = an object that transcends all computable functions describable
in finite terms. - ChatGPT in 2024

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-10-31  2:15 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-10-30  1:48 [FFmpeg-devel] [RFC] sponsors page Michael Niedermayer via ffmpeg-devel
2025-10-30  7:28 ` [FFmpeg-devel] " Steven Liu via ffmpeg-devel
2025-10-31  2:15   ` Michael Niedermayer via ffmpeg-devel

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