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>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 15:58:32 +0100
Message-ID: <CABGuwEm4Rz8vbG+qQ9NkYhYL9e77eezFfv682M=+8NBK0ZvuSA@mail.gmail.com> (raw)
In-Reply-To: <20250523113306.GY29660@pb2>
On Fri, May 23, 2025 at 12:33 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi Kieran
>
> On Fri, May 23, 2025 at 08:51:43AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> [...]
> > I appreciate the way the 2024 organisers ran STF was not exactly stellar
>
> It seems every mail you post is an attack on FFmpeg or the FFmpeg Team
> And its alot of different people you target. And often people who
> have done good and valuable work
>
> Seriously, I could easily talk negatively about you in every mail i
> write too but i dont, i try to be polite and positive.
>
> As an example i could have instead replied with a tone matching yours:
> (below is a (true) example of communication in the same tone as yours
> that i avoid)
>
> "I appreciated the stellar service you provided by providing and
> hosting a trac server for FFmpeg. It had only one broken cpu core.
> You only once decided to use the FFmpeg server to test some random
> audio hardware.
>
> Its sad that our users need reliable service"
Since you decided to slander me I looked at the logs.
I travelled two hours each way to the office on Saturday July 4th 2015
and stayed until 8pm on your request setting up a server as an
emergency.
This server was in the same room as two FFmpeg committers and a third
works for the same company remotely. These three contributors are
known physically to the community and have met the community many
times.
Many other FFmpeg developers also visited our office. This is in
contrast to the current hosting situation where nobody has visited,
nobody knows who has access.
I have no record of us ever testing an audio device in it. If we did
it was a real emergency.
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".
prev parent reply other threads:[~2025-05-23 14:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:42 Kieran Kunhya via ffmpeg-devel
2025-05-22 23:55 ` Devin Heitmueller
2025-05-23 3:48 ` Lynne
2025-05-23 14:37 ` Devin Heitmueller
2025-05-23 9:45 ` Michael Niedermayer
2025-05-23 9:58 ` Michael Niedermayer
2025-05-23 11:25 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:57 ` Devin Heitmueller
2025-05-23 15:59 ` Michael Niedermayer
2025-05-23 11:32 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:24 ` Tristan Matthews via ffmpeg-devel
2025-05-23 14:50 ` Devin Heitmueller
2025-05-23 15:00 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 15:45 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 20:35 ` Michael Niedermayer
2025-05-23 21:45 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:04 ` Michael Niedermayer
2025-05-23 3:44 ` Lynne
2025-05-23 6:50 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 9:53 ` Lynne
2025-05-23 7:51 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 11:33 ` Michael Niedermayer
2025-05-23 12:13 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:43 ` Michael Niedermayer
2025-05-24 16:39 ` [FFmpeg-devel] Previous trac server hosting Was: " Michael Niedermayer
2025-05-24 17:48 ` Kieran Kunhya via ffmpeg-devel
2025-06-02 4:29 ` Baptiste Coudurier
2025-05-23 14:58 ` Kieran Kunhya 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='CABGuwEm4Rz8vbG+qQ9NkYhYL9e77eezFfv682M=+8NBK0ZvuSA@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
/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