[FFmpeg-devel] [PATCH 2/3] doc/community: Conflict of interest recusal requirement (Similar to mid part of Antons proposal)

Rémi Denis-Courmont remi at remlab.net
Sun Mar 3 10:19:03 EET 2024


Le tiistaina 27. helmikuuta 2024, 0.44.37 EET Michael Niedermayer a écrit :
> Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>
> ---
>  doc/community.texi | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/doc/community.texi b/doc/community.texi
> index 8a38c6aca0..fc22a8fa61 100644
> --- a/doc/community.texi
> +++ b/doc/community.texi
> @@ -84,6 +84,9 @@ If the TC thinks it needs the input from the larger
> community, the TC can call f
> 
>  Each TC member must vote on such decision according to what is, in their
> view, best for the project.
> 
> +If a TC member is aware of a conflict of interest with regards to the case,
> they must announce it
> +and recuse themselves from the TC discussion and vote.

It looks like the meaning and intent do not match up here. I would expect 
something like either of:

* If a TC member is aware of being in a conflict of interest with regards to 
the case, they must announce it and recuse themselves from the TC discussion 
and vote.

* If a TC member is aware of a conflict of interest with regards to the case, 
they must announce it and the conflicted TC member(s) must recuse themselves 
from the TC discussion and vote.

But either way this leaves open what you do if somebody outside the TC asserts 
a conflict of interest against a TC member, or worse, if a conflict of interest 
is asserted post-facto. So in the end, while this rule seems well-meaning and 
agreeable, I don't see how you can avoid having conflicted TC member vote. 
Consequently, this should be a strong recommendation rather than a strict 
rule.

Again, the effective way to work-around this problem is to keep a large and 
diverse enough TC membership to offset the one or few hypothetical dishonest 
votes.

-- 
雷米‧德尼-库尔蒙
http://www.remlab.net/





More information about the ffmpeg-devel mailing list