Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [RFC] FFlabs Sponsor
Date: Sat, 11 Oct 2025 12:19:51 +0300
Message-ID: <13437903.I5CL7neSLu@basile.remlab.net> (raw)
In-Reply-To: <aOj8CikyPPyis76s@neo>

Le perjantaina 10. lokakuuta 2025, 15.28.58 Itä-Euroopan kesäaika Michael 
Niedermayer via ffmpeg-devel a écrit :
> The FFmpeg community decided, that we should actively look for sponsors.

Insofar as "absentees are always wrong" (French proverb), yes, but it should 
be noted that almost no one participated in that "decision".

> And to do that, i will use my influence as shareholder of FFlabs to (...)
> [donate] excess funds (...) to FFmpeg.

That statement gives the impression that you and/or the community expect that 
sort of behaviour out of sponsors. This seems more likely to put off 
prospective sponsors than motivate them, to be honest. You wouldn't typically 
announce sponsorships until after they are somewhat or fully committed.

It also looks like a discussion point that belongs in your shareholder 
meetings rather than FFmpeg-devel as others already pointed out. 

> Comments and Suggestion are welcome

Yeah: Don't comment publicly about future or ongoing specific sponsorship 
negotiations. Or at least ask yourself what do you think is more important and 
should be prioritised over the other:
- Holdng public discussion about getting sponsorships.
- Actually getting sponsorships.

-- 
德尼-库尔蒙‧雷米
Villeneuve de Tapiola, ex-République finlandaise d´Uusimaa



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

      parent reply	other threads:[~2025-10-11 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 12:28 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-10 14:02 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-10-10 14:07   ` Devin Heitmueller via ffmpeg-devel
2025-10-10 14:23     ` Michael Niedermayer via ffmpeg-devel
2025-10-10 14:33       ` Kieran Kunhya via ffmpeg-devel
2025-10-10 14:36         ` Nicolas George via ffmpeg-devel
2025-10-10 14:48           ` Kieran Kunhya via ffmpeg-devel
2025-10-11  9:19 ` Rémi Denis-Courmont 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=13437903.I5CL7neSLu@basile.remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /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