From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Democratization Date: Sat, 1 Feb 2025 21:18:01 +0100 Message-ID: <Z56BeXhZk2DlYKw3@phare.normalesup.org> (raw) In-Reply-To: <15008eae-ae84-4248-9afd-74b132481f5e@gmail.com> James Almer (12025-02-01): > It does by definition. A definition is not an argument by itself. A definition is a way for people to speak the same language when they state their arguments. Multiple people have said that we do not agree with that definition. > > (both me and nicolas for example liked the > > GA idea originally IIRC) also paul opposed it publically immedeatly YRC > And why did you stop liking the idea? When I realized that it gives the most power to the very people who have tried to take over the project. > As it's been said before, proposing to change a system because you were not > satisfied with the current one sets a bad precedent, and signals you're ok > with a democratic system as long as it's to your liking, not as long as it's > agreed by the people participating in it. It is exactly as it is, I only wish Michael would dare stating it as it is: “I am still the leader of this project, appointed to carry the legacy, and democracy is happening under my supervision. The way we have implemented it is not working, so I am changing it. Preferably with general approval.” > How many times are you going to repeat this? Thousands of registered emails > in a mailing list (of which a bunch are removed for excessive bouncing > almost daily) is not thousands of people active in a community. Users are part of the FFmpeg community too. That make millions of people, possibly billions. Do we give users a say in the future of the project? Yes, we do! If a user suggests an interesting feature, one of us may decide to implement it. It has happened many times. Do we give users a vote in the future of the project? Of course not. Many users ask for features because they misunderstand the correct way of achieving their goal. We will not implement those features just because they are many. The point: a user has a say in the future of the project in as much the suggestions of that users have merit. Merit: remember that word. > Those 49 are people that have kept the project alive and progressing for at > least the last five years. So these 49 people have done more for the project than the people who have contributed just one or two patches in all? You are saying that the condition to have a vote that you approve is based on the level of merit of contributors towards the project. I believe that you just admitted that FFmpeg is and should be not a democracy but a meritocracy. Excellent. Now we can discuss how to do it properly, because everybody equal until an arbitrary cutoff is one of the stupidest meritocracy conceivable. -- Nicolas George _______________________________________________ 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-02-01 20:18 UTC|newest] Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250102141731.GR4991@pb2> [not found] ` <20250102163807.GB7285@haasn.xyz> [not found] ` <20250114170615.GD4991@pb2> [not found] ` <eafdd773-0055-4619-b1e2-bf4d4266ee4e@gmail.com> [not found] ` <20250117173914.GN4991@pb2> [not found] ` <f5f57e16-8f34-4836-9b46-f31a753dd990@gmail.com> 2025-01-20 1:28 ` Michael Niedermayer 2025-01-20 6:21 ` Kieran Kunhya via ffmpeg-devel 2025-01-20 15:45 ` Soft Works 2025-01-20 16:15 ` Marth64 2025-01-20 16:38 ` Marth64 2025-01-21 0:36 ` Michael Niedermayer 2025-01-24 19:36 ` Rémi Denis-Courmont 2025-01-24 21:02 ` Nicolas George 2025-01-25 6:21 ` Rémi Denis-Courmont 2025-01-25 7:55 ` Vittorio Giovara 2025-01-25 20:26 ` Michael Niedermayer 2025-01-25 21:08 ` Rémi Denis-Courmont 2025-01-25 21:39 ` Rémi Denis-Courmont 2025-01-25 22:13 ` Marth64 2025-01-25 23:23 ` Kieran Kunhya via ffmpeg-devel 2025-01-25 22:40 ` Marth64 2025-01-26 15:06 ` Michael Niedermayer 2025-01-26 15:11 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 16:35 ` Rémi Denis-Courmont 2025-01-26 17:34 ` Marth64 2025-01-26 18:07 ` Marth64 2025-01-26 18:43 ` Gyan Doshi 2025-01-26 18:51 ` Marth64 2025-01-26 19:17 ` Michael Niedermayer 2025-01-26 19:39 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 20:40 ` Rémi Denis-Courmont 2025-01-26 20:51 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 21:20 ` Kieran Kunhya via ffmpeg-devel 2025-01-26 22:01 ` Marth64 2025-01-28 18:21 ` Michael Niedermayer 2025-01-29 6:40 ` Zhao Zhili 2025-01-29 12:39 ` Nicolas George 2025-01-29 15:16 ` Niklas Haas 2025-01-29 16:12 ` compn 2025-01-29 16:22 ` Vittorio Giovara 2025-01-29 17:02 ` Soft Works 2025-01-29 17:41 ` Marth64 2025-01-29 18:26 ` Marth64 2025-01-29 19:36 ` Kieran Kunhya via ffmpeg-devel 2025-01-29 20:20 ` Marth64 2025-01-29 20:54 ` Nicolas George 2025-01-29 21:08 ` Marth64 2025-01-29 21:45 ` Nicolas George 2025-01-30 6:12 ` Vittorio Giovara 2025-01-30 8:02 ` Nicolas George 2025-01-30 9:45 ` Vittorio Giovara 2025-01-31 0:03 ` Soft Works 2025-01-31 0:14 ` Vittorio Giovara 2025-02-01 13:50 ` Michael Niedermayer 2025-01-29 20:04 ` Ronald S. Bultje 2025-01-29 21:27 ` Niklas Haas 2025-01-29 21:39 ` Nicolas George 2025-02-01 14:15 ` Michael Niedermayer 2025-01-29 20:51 ` Nicolas George 2025-01-29 21:21 ` Niklas Haas 2025-01-29 21:36 ` Nicolas George 2025-01-30 6:08 ` Vittorio Giovara 2025-01-29 23:26 ` Soft Works 2025-01-30 6:35 ` Vittorio Giovara 2025-01-30 23:21 ` Soft Works 2025-01-31 0:14 ` Vittorio Giovara 2025-01-31 1:07 ` Soft Works 2025-01-30 9:50 ` Vittorio Giovara 2025-02-01 14:46 ` Michael Niedermayer 2025-02-01 14:48 ` Kieran Kunhya via ffmpeg-devel 2025-02-01 15:03 ` Michael Niedermayer 2025-02-01 16:10 ` Kieran Kunhya via ffmpeg-devel 2025-02-01 15:11 ` James Almer [not found] ` <dffa122a-f13a-4e95-8210-9053a6832e6a@e-blokos.com> 2025-02-01 16:03 ` James Almer 2025-02-01 20:18 ` Nicolas George [this message] 2025-02-01 13:44 ` Michael Niedermayer 2025-02-01 20:20 ` Nicolas George 2025-02-01 21:00 ` Soft Works 2025-01-29 9:45 ` Vittorio Giovara 2025-01-29 10:32 ` Soft Works 2025-01-29 10:51 ` Vittorio Giovara 2025-01-29 11:52 ` Soft Works 2025-01-29 14:38 ` Vittorio Giovara 2025-01-29 15:24 ` Soft Works 2025-01-29 16:24 ` Vittorio Giovara 2025-01-29 16:44 ` Soft Works 2025-01-30 8:02 ` Tobias Rapp 2025-01-29 16:58 ` Marth64 2025-01-29 17:06 ` Soft Works 2025-01-29 17:14 ` Marth64 2025-01-29 17:22 ` Soft Works 2025-01-29 17:38 ` Vittorio Giovara 2025-01-29 18:13 ` Soft Works 2025-01-29 18:23 ` Marth64 2025-01-29 17:15 ` Soft Works 2025-01-26 21:24 ` Michael Niedermayer 2025-01-26 21:41 ` Kieran Kunhya via ffmpeg-devel 2025-01-27 9:03 ` Vittorio Giovara 2025-01-20 17:44 ` Soft Works 2025-01-20 18:14 ` Gyan Doshi 2025-01-20 21:04 ` Nicolas George 2025-01-21 0:41 ` Michael Niedermayer 2025-01-21 6:52 ` Soft Works 2025-01-25 18:04 ` Michael Niedermayer 2025-01-24 20:01 ` Rémi Denis-Courmont 2025-01-20 17:59 ` Nicolas George 2025-01-20 18:18 ` Marth64 2025-01-20 18:46 ` Soft Works 2025-01-20 20:57 ` Nicolas George 2025-01-20 21:08 ` Marth64 2025-01-20 22:20 ` Marth64 2025-01-20 18:23 ` Marth64 2025-01-20 20:50 ` Nicolas George 2025-01-20 21:00 ` Soft Works 2025-01-21 0:55 ` Michael Niedermayer 2025-01-21 4:29 ` Marth64 2025-01-22 20:51 ` Nicolas George 2025-01-22 22:00 ` 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=Z56BeXhZk2DlYKw3@phare.normalesup.org \ --to=george@nsup.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