Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] The "bad" Patch
Date: Mon, 2 Jun 2025 21:22:29 +0000
Message-ID: <DM8P223MB0365B2679CD130494AAE7207BA62A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250602193438.GG29660@pb2>

> -----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.
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

- When each individual is able to see and understand their own actions
  within the full context, it allows them to reflect about how their
  own actions (even if just minimal) have contributed to the eventual
  outcome

- In the same way, people who weren't involved at all can learn from
  understanding those situations

The latter applies to myself as well, I'm sometimes writing faster than
thinking, which can lead to unintended consequences and there could 
very well be another case where I might have been documented as an 
actor. I don't consider myself standing out in this regard.

One fundamental difference though - and something that is badly 
missing in this community is the ability to admit one's own mistakes
and apologize as is appropriate. I always do that and the ML archive
gives testimony that this is true. It's an indication of integrity,
honesty and strength of personality and social competence.
Failing to do so is one of the seeds of toxicity towards each other.

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.


> > Because it seems you seriously care about stoping defamations and the
> > general sozial backstabbing that has appeared in the recent decade
> 
> “Seems” is the important word here.

I have been writing about these things here often before, in the 
hope that it makes people think about and reflect their own behavior.

If it would be true that it just "seems" that I would care, then I'd 
be curious about for which other reasons I'd be doing it then?


Best regards,
softworkz

_______________________________________________
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-06-02 21:22 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 . [this message]
2025-06-03  1:06                 ` Michael Niedermayer
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=DM8P223MB0365B2679CD130494AAE7207BA62A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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