Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] CC statement on alleged insults against the GSoC student et al
Date: Tue, 4 Mar 2025 13:15:01 -0600
Message-ID: <CAAhd_PW29E-=GcDAC0Sc_Ut7ytkC8UJ6U1xZx+v+qifibXfYWQ@mail.gmail.com> (raw)
In-Reply-To: <20250304181330.GP4991@pb2>

Hi Michael,

Thanks for your thoughts.

CC did not ignore. One can find a fault in that thread no matter which
lens it is looked under. Our conclusion is aimed to be balanced.
Objectively, Kieran's point was valid - the topic started with focus
on the complaint of our environment having a high learning ramp with
sometimes limited support, then it did evolve into out of context
concerns. While the delivery was not ideal as you pointed out, Kieran
cannot be singled out or faulted for this. We did issue a warning to
Kieran at the end of the statement, but the opportunity for cordial
delivery of tough messages is broader than just Kieran or this thread.
In fact, it is rampant in the community and will not improve
overnight.

We will continue to assess other complaints in our docket.

Best,
Marth64
_______________________________________________
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-03-04 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 15:35 Marth64
2025-03-04 15:56 ` Kieran Kunhya via ffmpeg-devel
2025-03-04 16:04   ` Rémi Denis-Courmont
2025-03-04 18:02 ` Michael Niedermayer
2025-03-04 19:00   ` Kieran Kunhya via ffmpeg-devel
2025-03-04 18:13 ` Michael Niedermayer
2025-03-04 19:15   ` Marth64 [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='CAAhd_PW29E-=GcDAC0Sc_Ut7ytkC8UJ6U1xZx+v+qifibXfYWQ@mail.gmail.com' \
    --to=marth64@proxyid.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