Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
Date: Sat, 8 Mar 2025 01:16:55 +0000
Message-ID: <DM8P223MB03654DB1904EF7182F2D1E57BAD42@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAAhd_PWTk2jnDjekgvrmO=CoPNH4DC6h7baRsRXS8eEMZAMHMg@mail.gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Marth64
> Sent: Samstag, 8. März 2025 01:22
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The Concept for the CC Installment is broken
> by Design
> 
> > I don't have any reason to think or say anything bad about you or
> other members of the CC.
> 
> Then I apologize if I misunderstood. I have no issue hearing criticism
> of our structures but the comparison to kindergartners came off the
> wrong way.
> _______________________________________________

Hi Marth64,

thanks and nevermind. I truly don't want to accuse anybody of anything and at the very least the members of the CC. I know about your intentions to improve the community and totally appreciate that.
I also have no doubts that you have done some good things which haven't become public. It's important to have community members like you who are trying to keep people together. 

My criticism is solely on the structure of the CC operations, which is based on many observations I had made during the past months. You - and the members of the CC - are taking your perceived integrity at stakes, solely for taking that role, not even due to any action that was taken. And when you take any (public) actions, some will always think it was wrong or will be dissatisfied. It's really a tough position to fulfil.
My overall impression is that the sole existence of the CC in the current form is more dividing than unifying, no matter what the CC does - and even when it would to nothing at all, the distrust that has emerged wasn't based on anything the CC has done, just about what it might be doing. Similar, the disregarding or CC members like being from this or that "group" or "party", like it had been alluded from various sides recently.
I wanted to illustrate the mechanism of and effects of the CC concept and how it can hardly fulfill the intended purposes in a beneficial way (in total sum) - no matter how good and faithful and passionate the people are who are taking those roles. Or let me put it this way: The CC structure is too much overshadowing the good things you are really intending to do.

The elementary school comparison is intended to illustrate which kind of system we have: making complaints privately and expecting the target being sanctioned publicly - that's not a healthy pattern. 
Btw. if you would really want to take it literally, you would be a teacher, not a child, but again, it was really not meant to call anybody a child or anything else, it was meant to make people think about the current system and how much sense it makes for this community.

Best wishes
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".

  reply	other threads:[~2025-03-08  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  4:36 Soft Works
2025-03-07  4:55 ` Soft Works
2025-03-07 22:42   ` Marth64
2025-03-07 23:56     ` Soft Works
2025-03-08  0:21       ` Marth64
2025-03-08  1:16         ` Soft Works [this message]
2025-03-08 10:50 ` Soft Works

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=DM8P223MB03654DB1904EF7182F2D1E57BAD42@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