Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2
Date: Mon, 3 Feb 2025 19:08:25 +0100
Message-ID: <20250203180825.GZ4991@pb2> (raw)
In-Reply-To: <45c37d06-f49b-42ff-a841-64cfaa513af4@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2989 bytes --]

Hi James

On Sun, Feb 02, 2025 at 03:14:58PM -0300, James Almer wrote:
> On 2/1/2025 6:53 PM, Michael Niedermayer wrote:
> > Hi James
> > 
> > On Sat, Feb 01, 2025 at 10:30:21AM -0300, James Almer wrote:
> > > On 1/31/2025 9:49 PM, Michael Niedermayer wrote:
> > > > Hi James
> > > > 
> > > > On Fri, Jan 31, 2025 at 12:44:50PM -0300, James Almer wrote:
> > > > > On 1/31/2025 11:58 AM, Nicolas George wrote:
> > > > > > Niklas Haas (12025-01-30):
> > > > [...]
> > > > > > On the other hand, I believe this whole plan is a bad idea.
> > > > > Yes, it is a bad idea. We have had the current system in place for about
> > > > > five years now, and besides one or two CC assemblages being inefficient, it
> > > > 
> > > > Do you remember this suggested addition to the FAQ ?
> > > > https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-January/338186.html
> > > > 
> > > > It seems you dont remember it even though this was posted just a few days ago
> > > > I knew this is needed to be put in the FAQ ;(
> > > 
> > > I saw it, and i think that patch is anything but objective and completely
> > > unacceptable. You're stating your opinion and discrediting a system in an
> > > official document in the project's repository itself of all places. Do you
> > > not see how absurd that is?
> > 
> > The system is absurd
> 
> The system is fine.

Then lets publish the FAQ i suggested (or a more formal text)
and let the reader judge it themselfs


> One CC was inefficient

It is not just one CC. And i would not choose the word "inefficient"


> and it bothered you

that really misses the point.

The CCs block moderators while allowing false statments to be published about
developers.
Its damaging to the people that are targetet and it created confusion and
disagreement where there is likely no actual significant disagreement
There are also several other serious issues with the CCs
(No public reporting / yearly reports / feedback to the voter)
(biased, treating some people differently)
(some CC members participated in attacks, both before and
 during their membership)
(some CC members did little, but no public reporting)
(one CC member called multiple developers assholes - then resigned
 - then was a candidates again - then resigned again)
...
And also iam happy to provide full references in public to any claim above


> to the point
> you want to start everything from scratch. It's not reasonable.

No, these are 2 seperate issues. The GA changes likely would not even fix
the CC issues.

Ill reply to the rest seperately to keep my replies short

thx

[...]


-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Dictatorship: All citizens are under surveillance, all their steps and
actions recorded, for the politicians to enforce control.
Democracy: All politicians are under surveillance, all their steps and
actions recorded, for the citizens to enforce control.

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

  reply	other threads:[~2025-02-03 18:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 20:33 Michael Niedermayer
2025-01-29 21:39 ` Leo Izen
2025-01-29 21:47   ` Nicolas George
2025-01-29 21:48   ` Soft Works
2025-01-30  6:38     ` Vittorio Giovara
2025-01-29 23:43 ` Niklas Haas
2025-01-30 18:04   ` Michael Niedermayer
2025-01-31 14:36     ` Nicolas George
2025-01-31 14:58   ` Nicolas George
2025-01-31 15:44     ` James Almer
2025-01-31 16:01       ` Soft Works
2025-02-02  2:25         ` Leo Izen
2025-02-02  3:37           ` Soft Works
2025-02-02  7:29           ` Vittorio Giovara
2025-02-01  0:49       ` Michael Niedermayer
2025-02-01  6:45         ` Zhao Zhili
2025-02-01 13:21           ` Ronald S. Bultje
2025-02-01 14:30             ` Vittorio Giovara
2025-02-01 14:11           ` Jean-Baptiste Kempf
2025-02-01 14:31             ` Vittorio Giovara
2025-02-02 11:34           ` Michael Niedermayer
2025-02-01 13:30         ` James Almer
2025-02-01 21:53           ` Michael Niedermayer
2025-02-02 18:14             ` James Almer
2025-02-03 18:08               ` Michael Niedermayer [this message]
2025-02-03 18:16                 ` Vittorio Giovara
2025-02-03 19:14               ` Michael Niedermayer
2025-02-03 20:45                 ` Nicolas George
2025-02-03  2:29             ` Ronald S. Bultje
2025-02-01 22:27           ` Michael Niedermayer
2025-02-01 22:29             ` Kieran Kunhya via ffmpeg-devel
2025-02-02 21:35             ` James Almer
2025-01-30  6:41 ` Vittorio Giovara
2025-02-01 20:44 ` Nicolas George
2025-02-02  0:01   ` Michael Niedermayer

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=20250203180825.GZ4991@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