Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Steven Liu via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
	Steven Liu <lingjiujianke@gmail.com>
Subject: [FFmpeg-devel] Re: [RFC] sponsors page
Date: Thu, 30 Oct 2025 15:28:40 +0800
Message-ID: <CADxeRw=8hpR5DVkKQgCBQM1GytKM3rqaPLPcyZjjSc0uaagNpQ@mail.gmail.com> (raw)
In-Reply-To: <aQLD1l3zW7FkONaG@neo>

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

      reply	other threads:[~2025-10-30  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30  1:48 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-30  7:28 ` Steven Liu via ffmpeg-devel [this message]

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='CADxeRw=8hpR5DVkKQgCBQM1GytKM3rqaPLPcyZjjSc0uaagNpQ@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=lingjiujianke@gmail.com \
    --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