From: Anton Khirnov <anton@khirnov.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule
Date: Tue, 20 Feb 2024 09:50:33 +0100
Message-ID: <170841903359.27417.409422117260058401@lain.khirnov.net> (raw)
In-Reply-To: <170841737762.27417.14992162535824834057@lain.khirnov.net>
My personal opinion is that broad interpretations of the rule in
question are highly undesirable, as they punish TC members for active
participation in the project. And since TC members tend to be among the
most active contributors, this can substantially reduce our already low
review rate, and lead to other perverse incentives - e.g. TC members
hiding their opinions for fear of losing their vote.
Moreover, I believe that arguments like "people should not sit in
judgement of their own patches" that sound common-sense reasonable on
the surface, are actually based on a misunderstanding of the notion of
conflict of interest and have no real basis.
The mandate of TC members is to use their technical expertise and
opinions to judge what is best for the project. Why should that be in
conflict with a TC member writing a patch - again according to their
judgement of what is best for the project? I believe there is no
conflict here, and thus no reason TC members could not vote on their own
patches, as long as they wrote those patches in accordance with their
mandate.
> The word 'involves' in it can be intepreted a variety of very different
> ways, to apply to TC members who e.g.:
> 1) authored the changes that are being objected to
> 2) are objecting to the changes
> 3) have any opinion on the changes, either positive or negative
> 4) have previously voiced an opinion that would apply to the changes
> 5) authored the code that is being modified
> 6) have a financial or other similar interest in a specific outcome of
> the disagreement
So IMO the only case that needs to be excluded is 6) - an actual
conflict of interest. I therefore propose the following wording changes:
--- a/doc/community.texi
+++ b/doc/community.texi
-If the disagreement involves a member of the TC, that member should recuse themselves from the decision.
+ Each TC member must vote on such decision according to what is, in their
+ view, best for the project. If a TC member is affected by a conflict of
+ interest with regards to the case, they must announce it and recuse
+ themselves from the TC discussion and vote. A conflict of interest is
+ presumed to occur when a TC member has a personal interest (e.g.
+ financial) in a specific outcome of the case.
--
Anton Khirnov
_______________________________________________
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 8:51 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 [this message]
2024-02-20 9:12 ` Marton Balint
2024-02-20 9:21 ` Anton Khirnov
2024-02-20 19:32 ` Marton Balint
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=170841903359.27417.409422117260058401@lain.khirnov.net \
--to=anton@khirnov.net \
--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