Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
	Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel]  FFmpeg Community Committee – Updates & Next Steps
Date: Sat, 24 May 2025 18:57:22 +0100
Message-ID: <CABGuwEkioKvCLiiXpTnEkuVpE_+1ObDW4pX=fUyQUJwqAcr-Qw@mail.gmail.com> (raw)
In-Reply-To: <CABGuwEnDGOk4j3WF3s64PRm6PXRU41khmidxA6Rq18pSF9k1yA@mail.gmail.com>

On Tue, 4 Mar 2025, 19:01 Kieran Kunhya, <kieran618@googlemail.com> wrote:

>
>
> On Tue, 4 Mar 2025, 11:17 Michael Niedermayer, <michael@niedermayer.cc>
> wrote:
>
>> Hi Kieran
>>
>> On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel
>> wrote:
>> [...]
>> > Hi Michael,
>> >
>> > Was all the STF discussion around the first application done in public?
>>
>> No, jb contacted STF in the name of FFmpeg without any public discussion.
>> This crossed STFs own reaching out to FFmpeg. Which is how it was noticed
>>
>> The mail below is from STF to jb.
>>
>> After that i immedeatly asked both thilo and jb to talk with each other.
>> I also repeatedly asked for the STF stuff to be made public.
>> I quote a rather sarcastic example from me (in german) asking thilo at
>> the end
>> of this mail
>>
>> So again, we need more open communication, more forgiveness, more working
>> together and less distrust, some virtual hugs and smiles
>>
>>
>> From: Tara Tarakiyee <X>
>> To: jb@X
>> Cc: "Fiona Krakenbürger" <X>, Abigail Garner <X>
>> Subject: Regarding Your STF Application
>> Date: Tuesday, 30 May 2023 22:22
>>
>> Dear Jean-Baptiste Kempf,
>>
>> Thank you for your application to the Sovereign Tech Fund. We appreciate
>> the interest, but have a few questions about the timing of this
>> application. We have already reached out to ffmpeg maintainers through our
>> scouting process and gotten a response and arranged a call. We explained
>> how our funding works and asked that they go back to the ffmpeg maintainer
>> community and come back to us with a joint proposal that is agreed upon by
>> your existing governance structure.
>>
>> Given the timing of your proposal, are we to infer that you knew about
>> those conversations yet choose to apply independently? We much prefer to
>> have one process ongoing at the time, so we ask that you refer back to that
>> conversation and include your work there and we will continue considering
>> our support for ffmpeg through our scouting. If that is not possible for
>> some reason, please let us know.
>>
>> Please keep in mind that our mission at STF is to empower FOSS
>> infrastructure, so we support activities to improve security and
>> maintenance, but very rarely support new feature development, except when
>> there is a strong case for them in the public interest. Also it is
>> important for us that any supported work has the support of the maintainer
>> community.
>>
>> Please let me know if you have any questions.
>>
>> Best wishes,
>> Tara Tarakiyee
>> Sovereign Tech Fund
>> https://sovereigntechfund.de/
>>
>> SPRIND GmbH
>> BUNDESAGENTUR
>> FÜR SPRUNGINNOVATIONEN
>>
>> Lagerhofstraße 4
>> 04103 Leipzig
>>
>> Geschäftsführung: Berit Dannenberg, Rafael Laguna de la Vera
>> Vorsitzender des Aufsichtsrats: Dr.-Ing. E. h. Peter Leibinger
>> Amtsgericht Leipzig – HRB 36977 – USt-ID DE328253854
>>
>>
>>
>> Date: Thu, 1 Jun 2023 18:37:13 +0200
>> From: Michael Niedermayer <michael@niedermayer.cc>
>> To: Thilo Borgmann <X>
>> Subject: Re: FFmpeg development support
>>
>> > Michael, er hat bereits versucht, das alles im Dunkeln abzuwickeln. Er
>> hat bereits einen Antrag eingereicht, den er _nicht_ geteilt hat und auch
>> auf Nachfrage _nicht_ teilt. Nur dummerweise hat er uns von der Sache an
>> sich erzählt und dummerweise, ist ihm das auf die Füße gefallen.
>> > Es gibt einen Grund, warum er darüber auch immernoch nicht redet,
>> Michael. Warum denkst du, steht in seiner Mail nur "Habt ihr davon gehört?"
>> ?...
>>
>> Thilo dein Antrag ist public auf der mailing liste (und wiki) ?
>> nein?
>> wenn nein dann was ist es dunkles was du planst ?
>>
>
> Please (as per your own declaration of transparency) therefore supply the
> rest of the email chain including all discussion with Thilo and/or other
> parties (e.g SPI) about STF.
>
> Kieran
>

Hi Michael,

I'm still waiting for this. Seeing as you are happy to leak private
conversations at will (both me, the CC, FFlabs and others), it's
interesting you've been so silent about this

I wonder why?

Kieran

>
_______________________________________________
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-05-24 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 23:04 Marth64
2025-02-26  1:51 ` Michael Niedermayer
2025-02-26 14:22   ` Vittorio Giovara
2025-02-26 22:33     ` Kieran Kunhya via ffmpeg-devel
2025-02-26 23:11   ` Jean-Baptiste Kempf
2025-02-27 18:18     ` Michael Niedermayer
2025-02-27 22:41       ` Vittorio Giovara
2025-02-28  7:13         ` compn
2025-02-28 13:48           ` Vittorio Giovara
2025-02-27 23:00       ` Marth64
2025-02-28 19:27         ` Michael Niedermayer
2025-02-28 20:35           ` Vittorio Giovara
2025-02-28 19:29         ` Michael Niedermayer
2025-03-02 10:16           ` Rémi Denis-Courmont
2025-03-05 18:43             ` compn
2025-03-04  2:35     ` Michael Niedermayer
2025-03-04 14:13       ` Kieran Kunhya via ffmpeg-devel
2025-03-04 17:17         ` Michael Niedermayer
2025-03-04 19:01           ` Kieran Kunhya via ffmpeg-devel
2025-05-24 17:57             ` Kieran Kunhya via ffmpeg-devel [this message]
2025-02-26 23:51   ` James Almer

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='CABGuwEkioKvCLiiXpTnEkuVpE_+1ObDW4pX=fUyQUJwqAcr-Qw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.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