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 <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Wed, 23 Jul 2025 11:59:23 +0200
Message-ID: <20250723095923.GJ29660@pb2> (raw)
In-Reply-To: <CABGuwE=WmY27x0JY-4zs0A+GYNHQ_qKrYXZ--6p8uM0vxCuCqw@mail.gmail.com>


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

Hello Kieran

On Wed, Jul 23, 2025 at 10:39:01AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> >
> >
> >
> > About 2. (IMHO)
> > * The solution is to hire carl or someone else (or find a volunteer)
> >   to do this work. Changing the tracker will not fix this.
> >
> >   FFlabs should have  enough captial to hire carl for this. People should
> > ask
> >   FFlabs to hire him and carl to accept to be hired for this work.
> 
> 
> The commercial decisions of FFlabs are for its shareholders during its
> internal meetings, not this mailing list.

Thats a misunderstanding.

Let me quote the president and CEO:

"The company is just a way to finance the community to work on the same
 things as usual."

and

"To me, the company should be transparent to the project. It's just a way
 to funnel money to the community."


thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The educated differ from the uneducated as much as the living from the
dead. -- Aristotle 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-07-23  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  3:53 Lynne
2025-07-22  8:44 ` Kacper Michajlow
2025-07-22  9:15   ` Jacob Lifshay
2025-07-23  4:05   ` Lynne
2025-07-22 15:01 ` Leo Izen
2025-07-23  4:01   ` Lynne
2025-07-22 23:04 ` Michael Niedermayer
2025-07-23  4:01   ` Lynne
2025-07-23  9:16     ` Michael Niedermayer
2025-07-23  9:39       ` Kieran Kunhya via ffmpeg-devel
2025-07-23  9:59         ` Michael Niedermayer [this message]
2025-07-23 10:02           ` Kieran Kunhya via ffmpeg-devel
2025-07-23 11:48           ` Nicolas George
2025-07-23  9:38     ` Michael Niedermayer
2025-07-23 11:49       ` Nicolas George

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=20250723095923.GJ29660@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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