From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] Democratization work in progress draft v2 Date: Fri, 31 Jan 2025 12:44:50 -0300 Message-ID: <9dacff42-0536-4736-922b-0d791d63ef61@gmail.com> (raw) In-Reply-To: <Z5zk-DFzE0N3SMSD@phare.normalesup.org> [-- Attachment #1.1.1: Type: text/plain, Size: 2098 bytes --] On 1/31/2025 11:58 AM, Nicolas George wrote: > Niklas Haas (12025-01-30): >> This should be time-gated to count only commits in the recent, say, 3 >> years (to match the current GA cycle). Counting purely historical >> commits seems odd. > > On the other hand, we should give more weight to the opinion of people > who have been around for many years and obviously intend to stay than to > the opinion of people who have been here for a few months and will leave > after two or three job missions. Is this level of discredit necessary or useful for the discussion? And how many people have met the requisites after only a few months of contributions before leaving? Not to mention the GA does not get updated on the fly, but gets refreshed in specific intervals, so anyone who just dumps some code then leaves immediately is unlikely to even make it in, and if they do, they'd barely last. > > Past involvement, including long-past involvement, is not only past, it > is both indication of knowledge about the project and prediction of > future involvement. > > For that reason, I believe that if this plan goes forward, it should > include all past involvement, but possibly with the condition that the > involvement continues presently. This we all agree with. If someone has contributed code a long time ago and wants a voice, they should at least be active in some form. It's the case of a few proposed GA additions that did not met the commit criteria and were then accepted. > > 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 has worked. Changing it now because one person was unhappy with a CC (That was literally on the way out, in fact) sets a bad precedent, because then anyone that dislikes agreed decisions will want to redo everything from scratch in the hopes a new system will be more to their liking, and the bikesheding and filibustering will never end. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 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".
next prev parent reply other threads:[~2025-01-31 15:45 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 [this message] 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 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=9dacff42-0536-4736-922b-0d791d63ef61@gmail.com \ --to=jamrial@gmail.com \ --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