From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Thu, 24 Jul 2025 18:05:12 -1000
Message-ID: <20250724180512.00007b6a@hawaiiantel.net> (raw)
In-Reply-To: <20250723095923.GJ29660@pb2>
On Wed, 23 Jul 2025 11:59:23 +0200, Michael Niedermayer wrote:
> 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."
>
hello,
fflabs should have its use and goals documented on its
website https://fflabs.eu/services/
otherwise, the fflabs website looks like it hasnt been updated in 2
years, is written in broken english, and looks like just an organization
to hire consultants.
said another way, fflabs doesnt look like anything to do with the ffmpeg
community. at all. besides being some ffmpeg developers for consultant
work.
https://www.linkedin.com/company/fflabs/
"FFLABS is a FFmpeg consulting company"
does not sound like a community focused company at all.
-compn
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-25 4:05 UTC|newest]
Thread overview: 40+ 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-25 3:40 ` compn
2025-07-25 3:58 ` Jacob Lifshay
2025-07-25 4:36 ` compn
2025-07-25 11:41 ` Nicolas George
2025-07-25 14:20 ` Kieran Kunhya via ffmpeg-devel
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
2025-07-23 10:02 ` Kieran Kunhya via ffmpeg-devel
2025-07-23 11:48 ` Nicolas George
2025-07-25 4:05 ` compn [this message]
2025-07-26 14:57 ` Michael Niedermayer
2025-07-23 9:38 ` Michael Niedermayer
2025-07-23 11:49 ` Nicolas George
2025-07-26 17:03 ` Derek Buitenhuis
2025-07-26 19:29 ` Timo Rothenpieler
2025-07-26 20:01 ` Derek Buitenhuis
2025-07-26 20:14 ` Timo Rothenpieler
2025-07-26 20:24 ` Kacper Michajlow
2025-07-26 20:29 ` Derek Buitenhuis
2025-07-26 20:41 ` Timo Rothenpieler
2025-07-26 20:45 ` Derek Buitenhuis
2025-07-26 21:07 ` Kacper Michajlow
2025-07-26 21:18 ` Timo Rothenpieler
2025-07-26 22:44 ` Michael Niedermayer
2025-07-26 22:57 ` Timo Rothenpieler
2025-07-26 22:48 ` Michael Niedermayer
2025-07-26 20:28 ` Derek Buitenhuis
2025-07-26 20:14 ` Kacper Michajlow
2025-07-26 20:23 ` Timo Rothenpieler
2025-07-26 20:29 ` Kacper Michajlow
2025-07-26 20:33 ` Derek Buitenhuis
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=20250724180512.00007b6a@hawaiiantel.net \
--to=ff@hawaiiantel.net \
--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