From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule Date: Tue, 20 Feb 2024 20:32:19 +0100 (CET) Message-ID: <cd3005d8-ca5a-dc4d-ce75-a7d1aa4cc8ae@passwd.hu> (raw) In-Reply-To: <170842089279.31318.2654441079015212247@lain.khirnov.net> On Tue, 20 Feb 2024, Anton Khirnov wrote: > Quoting Marton Balint (2024-02-20 10:12:34) >> We have no means to prove financial interest, because it is not public. > > We also have no means to prove that committee members are acting in the > project's interest. > > E.g. if I had no qualms about being dishonest, I could always ask a > friend to object to controversial patches in my place, so I wouldn't > lose my vote, and nobody could prove it. > > In the end some things have to be taken on trust. My concern is bad mouthing others based on assumed financial interest and endless discussion if that interest is "serious" or not. If your payjob uses ffmpeg, or if you ever want money for some ffmpeg related work, that is a financial interest right there. If somebody feels that voting would not be fair, he can always abstain. I'd rather keep that fully trust based, to avoid rule interpretation wars and discussions about assumed interests. An interest is not inherently bad, selfish contributions (financial reasons or not) is a huge factor in open source. > >> For practical reasons, using patch authorship is better. Or maybe a more >> general solution against bias is somewhat increasing the number of people >> in the TC, and removing this rule alltogether. > > I woould be concerned about making the TC too slow and unwieldy, it > already takes a lot of effort to push any decisions through. Keep in > mind that during all of its existence it only ever made two decisions, > and one of them spent over a year in limbo. So with 7 people, it would have been two years? :) Have the TC meet weekly if there is an agenda, and have votes after meeting. With more people it is not that big of a deal if somebody cannot attend. And have a rule in place to resolve ties. It can be as simple as to accept the proposal of the party who raised the issue to the TC. Regards, Marton _______________________________________________ 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:[~2024-02-20 19:32 UTC|newest] Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-20 8:22 Anton Khirnov 2024-02-20 8:50 ` Anton Khirnov 2024-02-20 9:12 ` Marton Balint 2024-02-20 9:21 ` Anton Khirnov 2024-02-20 19:32 ` Marton Balint [this message] 2024-02-22 21:34 ` Anton Khirnov 2024-02-20 10:01 ` Gyan Doshi 2024-02-20 11:09 ` Anton Khirnov 2024-02-22 6:50 ` Gyan Doshi 2024-02-22 21:21 ` Anton Khirnov 2024-02-23 7:56 ` Nicolas George 2024-02-23 10:56 ` Gyan Doshi 2024-02-23 14:18 ` Nicolas George 2024-02-23 14:52 ` Zhao Zhili 2024-02-23 16:05 ` Anton Khirnov 2024-02-23 19:36 ` Ronald S. Bultje 2024-02-26 16:33 ` Anton Khirnov 2024-02-26 18:12 ` Ronald S. Bultje 2024-02-26 19:17 ` Anton Khirnov 2024-02-26 19:48 ` Ronald S. Bultje 2024-02-26 20:02 ` Anton Khirnov 2024-02-26 20:30 ` Rémi Denis-Courmont 2024-02-26 20:44 ` Nicolas George 2024-02-20 20:50 ` Niklas Haas 2024-02-22 21:14 ` Anton Khirnov 2024-02-23 23:27 ` Michael Niedermayer 2024-02-24 11:05 ` Paul B Mahol 2024-02-26 16:52 ` Anton Khirnov 2024-02-26 22:47 ` Michael Niedermayer 2024-02-27 7:20 ` Anton Khirnov 2024-02-27 16:55 ` Michael Niedermayer 2024-03-01 16:50 ` Anton Khirnov 2024-02-20 14:01 ` Michael Niedermayer 2024-02-20 14:18 ` Rémi Denis-Courmont 2024-02-20 16:10 ` Anton Khirnov 2024-02-20 20:41 ` Michael Niedermayer [not found] ` <3C1074B4-096B-4806-BFB0-9D491E148C48@cosmin.at> 2024-02-20 21:12 ` Cosmin Stejerean via ffmpeg-devel 2024-02-20 21:51 ` Michael Niedermayer 2024-02-22 21:54 ` Anton Khirnov 2024-02-23 14:25 ` Michael Niedermayer 2024-02-20 16:07 ` Nicolas George 2024-02-20 19:57 ` Rémi Denis-Courmont 2024-02-22 21:16 ` Anton Khirnov 2024-02-23 14:00 ` Michael Niedermayer 2024-02-23 14:15 ` Nicolas George 2024-02-23 16:07 ` Anton Khirnov 2024-03-01 17:33 ` Anton Khirnov 2024-03-02 5:37 ` Gyan Doshi 2024-03-02 19:01 ` Ronald S. Bultje [not found] ` <3EB2D263-CAB5-4096-A061-D880D4BE95F6@cosmin.at> 2024-03-02 19:08 ` Cosmin Stejerean via ffmpeg-devel 2024-03-03 1:34 ` Michael Niedermayer 2024-03-03 7:23 ` Gyan Doshi 2024-03-03 2:49 ` Michael Niedermayer 2024-03-03 21:57 ` Anton Khirnov 2024-03-03 23:36 ` Michael Niedermayer 2024-03-03 23:56 ` Michael Niedermayer 2024-03-05 18:38 ` Niklas Haas 2024-03-05 19:02 ` Nicolas George 2024-03-04 21:15 ` Anton Khirnov 2024-03-05 2:36 ` Michael Niedermayer 2024-03-05 10:23 ` Anton Khirnov 2024-03-04 0:57 ` Michael Niedermayer 2024-03-04 9:45 ` Vittorio Giovara 2024-03-05 2:50 ` Michael Niedermayer 2024-03-05 10:27 ` Anton Khirnov 2024-03-06 23:25 ` Michael Niedermayer via ffmpeg-devel 2024-03-07 3:37 ` Zhao Zhili 2024-03-07 14:01 ` Vittorio Giovara 2024-03-08 13:16 ` Paul B Mahol 2024-03-05 12:44 ` Vittorio Giovara 2024-03-06 2:06 ` Michael Niedermayer 2024-03-22 12:52 ` Anton Khirnov 2024-03-22 13:01 ` Nicolas George 2024-03-22 13:05 ` Gyan Doshi 2024-03-25 9:41 ` Anton Khirnov 2024-03-25 12:10 ` Gyan Doshi 2024-03-25 14:49 ` Anton Khirnov 2024-03-24 2:21 ` Michael Niedermayer 2024-03-24 11:40 ` Anton Khirnov 2024-03-24 23:44 ` Michael Niedermayer 2024-03-25 9:44 ` Anton Khirnov 2024-03-26 8:20 ` Anton Khirnov 2024-03-26 22:14 ` Michael Niedermayer 2024-03-29 11:39 ` Anton Khirnov 2024-03-29 19:52 ` Michael Niedermayer 2024-04-01 11:16 ` Anton Khirnov 2024-04-01 12:20 ` Gyan Doshi 2024-04-01 13:07 ` Anton Khirnov 2024-04-01 14:59 ` Michael Niedermayer 2024-04-01 15:46 ` Paul B Mahol 2024-04-01 15:41 ` Paul B Mahol
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=cd3005d8-ca5a-dc4d-ce75-a7d1aa4cc8ae@passwd.hu \ --to=cus@passwd.hu \ --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