From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] [RFC] financial sustainability Plan A (SPI)
Date: Fri, 27 Oct 2023 18:52:51 +0000
Message-ID: <0101018b727b6479-03fc0e78-9c0a-4ac6-9cc3-53f13d5590fd-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <1841453.XJlOWdci6N@basile.remlab.net>
> On Oct 27, 2023, at 9:14 AM, Rémi Denis-Courmont <remi@remlab.net> wrote:
>
>> Consider FFlabs, you can look at who is being paid by FFlabs, its being
>> mentioned in various places.
>> Then look at what these people do, so you know what they are paid for.
>
> I don't know if FFlabs publishes the payments it makes to its consultants, so
> I can't answer your question. But it sounds odd, as I would expect that that
> would violate privacy laws. All FFlabs seems to publish is who their
> consultants are, not what they work on or for.
With a list of FFLabs consultants the "what they work on" can be extracted from the git log or mailing list patches. Not who is paying for the work or how much is being paid, but certainly the what can be inferred with a reasonable degree of accuracy.
- Cosmin
_______________________________________________
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:[~2023-10-27 18:53 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:45 Michael Niedermayer
2023-10-26 19:02 ` Kieran Kunhya
2023-10-26 19:41 ` Thilo Borgmann via ffmpeg-devel
2023-10-27 1:28 ` Kieran Kunhya
2023-10-27 10:23 ` Thilo Borgmann via ffmpeg-devel
2023-10-27 13:38 ` Kieran Kunhya
2023-10-27 15:08 ` Thilo Borgmann via ffmpeg-devel
2023-10-27 15:38 ` Rémi Denis-Courmont
2023-10-27 12:20 ` Michael Niedermayer
2023-10-27 10:43 ` Rémi Denis-Courmont
2023-10-27 11:10 ` Thilo Borgmann via ffmpeg-devel
2023-10-27 11:30 ` Rémi Denis-Courmont
2023-10-27 12:24 ` Thilo Borgmann via ffmpeg-devel
2023-10-27 15:24 ` Rémi Denis-Courmont
2023-10-27 16:05 ` Michael Niedermayer
2023-10-27 16:14 ` Rémi Denis-Courmont
[not found] ` <AD4E0E39-49ED-4C96-8C12-9EAF6AFC00B0@cosmin.at>
2023-10-27 18:52 ` Cosmin Stejerean via ffmpeg-devel [this message]
2023-10-27 19:00 ` Rémi Denis-Courmont
[not found] ` <5F5D6E6A-D85E-43E1-AF5B-B5CFBE60BF94@cosmin.at>
2023-10-27 19:04 ` Cosmin Stejerean via ffmpeg-devel
2023-10-27 12:27 ` Michael Niedermayer
2023-10-27 12:32 ` Michael Niedermayer
2023-10-27 13:46 ` Kieran Kunhya
2023-10-27 15:08 ` Michael Niedermayer
2023-10-28 14:20 ` Ronald S. Bultje
2023-10-28 15:30 ` Thilo Borgmann via ffmpeg-devel
2023-10-28 16:43 ` Ronald S. Bultje
2023-10-28 17:21 ` Michael Niedermayer
2023-10-28 18:01 ` Michael Niedermayer
2023-10-28 18:58 ` Paul B Mahol
2023-10-28 20:46 ` Michael Niedermayer
2023-10-29 14:35 ` Rémi Denis-Courmont
2023-10-29 16:12 ` Michael Niedermayer
2023-10-29 16:22 ` Kieran Kunhya
2023-10-29 19:36 ` Rémi Denis-Courmont
2023-10-31 16:58 ` Michael Niedermayer
2023-10-31 17:19 ` Rémi Denis-Courmont
2023-10-31 17:31 ` Michael Niedermayer
2023-10-31 17:37 ` Hendrik Leppkes
2023-10-31 17:48 ` Michael Niedermayer
2023-11-01 0:04 ` Thilo Borgmann via ffmpeg-devel
2023-11-01 1:27 ` Steven Liu
2023-10-29 16:47 ` Nicolas George
2023-10-29 19:43 ` Ronald S. Bultje
2023-10-29 19:46 ` Nicolas George
2023-10-29 19:53 ` Ronald S. Bultje
2023-10-29 20:10 ` Paul B Mahol
2023-10-29 20:03 ` Rémi Denis-Courmont
2023-10-29 20:43 ` Nicolas George
2023-10-28 21:17 ` Kieran Kunhya
2023-10-29 15:40 ` Michael Niedermayer
2023-10-28 17:21 ` Thilo Borgmann via ffmpeg-devel
2023-10-30 7:32 ` Gijs Peskens
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=0101018b727b6479-03fc0e78-9c0a-4ac6-9cc3-53f13d5590fd-000000@us-west-2.amazonses.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cosmin@cosmin.at \
/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