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: Sun, 1 Jun 2025 23:51:30 +0000
Message-ID: <DM8P223MB036504ECC5A64598EF278B75BA63A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250601232143.GA29660@pb2>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Montag, 2. Juni 2025 01:22
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
> On Sat, May 31, 2025 at 05:34:14PM +0000, softworkz . wrote:
> > CONCLUSIONS
> > ===========
> >
> > Meanwhile it should have become clear that this conversation is not about
> > whether the 15/15 patchset gets or should have gotten included or not.
> > It's about the things that happened around it and how they happened:
> >
> > => False statements like I would have pushed without addressing all reviews
> >
> > => A patch that was quickly brandmarked even though almost nobody had looked
> at it
> > without any discussion and assessment
> >
> > => Claims like "softworkz is pushing bad patches"
> >
> > => softworkz shouldn't have been given commit rights
> >
> > => it's the worst patchset in the history of the project
> >
> >
> > That chain of events is what is just not acceptable.
> > It is in no way adequate or appropriate.
> >
> > Everybody who has been part of that chain should think about this.
> > I'm sure that many didn't have the intention to achieve this outcome.
> >
> > But unfortunately, there's one or another who has worked on moving this
> > forward in a way to achieve that outcome exactly.
> > To those persons, I want to be very clear: Trying those things on me will
> > never work out, as I will always try 10 times harder against it and the
> > result for those will be very different and more impactful in case anybody
> > would ever try again to strategically and purposefully and against better
> > knowledge defame or discredit me.
> >
> >
> > I don't want all this. I don't want to deal with such things, I just want
> > to collaborate in a friendly and professional way. Anybody - without
> > exception - who is getting back to me in a friendly way will receive a
> > friendly response, no matter what happened yesterday. I have no hard
> feelings
> > in this at all - it's just work and it has been pretty annoying that
> > I had to write all those messages. Still, I cannot leave all those untrue
> > statements lying around without context.
> >
> > You will see a number of messages which are linking to this conversation
> > from other conversations. I apologize in advance for that spam, but it
> > wasn't me who created the situation.
>
> Not sure if 90% of people agree or 90% disagree with me but
> Id like you to be in the next community committee. (together with marth64)
>
> Because it seems you seriously care about stoping defamations and the
> general sozial backstabbing that has appeared in the recent decade
>
> and also documenting precissely what everyone said.
>
> Just seems these attributes would be valuable for the community committee
>
Hi Michael,
thanks a lot for the friendly words. Essentially, I do care about community
behavior and even more about being truthful and honest.
I'm not sure whether I would be a suitable member for the CC. I think these
positions need to occupied by persons who are trusted by many in the
community and I'm well aware that some have reservations towards me - which
I can perfectly understand. I have been loud at times and voiced minority
opinions. Others may have longer lists 😊
In general, there are many qualities I have to offer, but I would say that
mediation and diplomatic negotiations are not in a top position there.
From what I've seen some of the current CC members writing, those guys are
much more suitable for the job than I would be.
But thanks for suggesting me,
sw
_______________________________________________
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-01 23:51 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 . [this message]
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
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=DM8P223MB036504ECC5A64598EF278B75BA63A@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