From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] The "bad" Patch
Date: Tue, 3 Jun 2025 03:06:01 +0200
Message-ID: <20250603010601.GH29660@pb2> (raw)
In-Reply-To: <DM8P223MB0365B2679CD130494AAE7207BA62A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 2575 bytes --]
Hi
On Mon, Jun 02, 2025 at 09:22:29PM +0000, softworkz . wrote:
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> > Niedermayer
> > Sent: Montag, 2. Juni 2025 21:35
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] The "bad" Patch
> > 
> 
> Hi,
> 
> > The CC needs someone who is good at mediating (or what you call it) thats
> > marth64
> 
> +1
> 
> 
> > And the CC needs someone who can recognize defamation and document it
> > accurately. Ive not seen anyone except softworkz document things as he did.
> 
> Admittedly, the motivation was high, since I've been in focus. Naturally,
> I had been upset about specific persons at the beginning, but the more I 
> had reconstructed the sequence of events, I realized that the way how 
> things had developed and escalated further,
> was more complex and driven
> by many actors, most of which never had much bad intentions and acted
> without being aware about the consequences of their own actions.
+1
I believe 99.9% of people have good intentions on this ML not 100% though
> Asked about it, I'm sure most of them would think and say that they would
> have had nothing to do with it at all and it wasn't their own fault.
> But in a community, when several people do just little wrong 
> individually, this can sum up very quickly and easily.
> 
> The motivations behind documenting the events are multifold:
> 
> - When we better understand the origins and mechanisms of how that 
>   "toxicity" is formed and unfolds, then we might better be able to
>   take measures to reduce it in the future
+1
I belive documenting things is the first step in solving them.
[...]
> 
> To me, it seems that people are afraid that this could be taken as
> weakness or incompetence - which is a fundamental misconception.
> Even in technical discussions, I see that people rather stop 
> responding than admitting, when they realize they were wrong about
> something. But the opposite is true: not admitting is weak
> behavior.
Theres alot of variation here i think
from not even internally admiting to people who do admit publically they
where wrong.
and also people stoping responding when a discussion becomes too toxic
(as in "dont feed the trolls")
thx
[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-06-03  1:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 15:24 softworkz .
2025-05-28 17:34 ` Rémi Denis-Courmont
2025-05-28 18:01   ` softworkz .
2025-05-28 18:09     ` softworkz .
2025-05-28 18:27 ` Marton Balint
2025-05-28 18:46   ` softworkz .
2025-05-29  2:59 ` softworkz .
2025-05-29  9:55   ` Nicolas George
2025-05-31 11:44   ` softworkz .
2025-05-31 16:21     ` Mark Thompson
2025-05-31 18:28       ` softworkz .
2025-05-31 20:26         ` Mark Thompson
2025-06-02  6:09           ` softworkz .
2025-06-02  7:31           ` softworkz .
2025-05-31 16:59     ` softworkz .
2025-05-31 17:34       ` softworkz .
2025-06-01 23:21         ` Michael Niedermayer
2025-06-01 23:51           ` softworkz .
2025-06-02  7:57           ` Nicolas George
2025-06-02  9:31             ` softworkz .
2025-06-02 10:18               ` softworkz .
2025-06-02 10:49                 ` Nicolas George
2025-06-02 19:30                   ` softworkz .
2025-06-02 21:26                   ` softworkz .
2025-06-02 19:34             ` Michael Niedermayer
2025-06-02 21:22               ` softworkz .
2025-06-03  1:06                 ` Michael Niedermayer [this message]
2025-06-01 23:56         ` softworkz .
2025-05-31 18:38       ` Kieran Kunhya via ffmpeg-devel
2025-05-29 14:43 ` Nicolas George
2025-05-30  3:42   ` softworkz .
2025-05-31 19:31 ` Leo Izen
2025-05-31 19:34   ` Marvin Scholz
2025-05-31 20:08   ` softworkz .
2025-05-31 20:13     ` softworkz .
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=20250603010601.GH29660@pb2 \
    --to=michael@niedermayer.cc \
    --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