From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/3] doc/community: Conflict of interest recusal requirement (Similar to mid part of Antons proposal)
Date: Sun, 03 Mar 2024 10:19:03 +0200
Message-ID: <5680631.yRUoJKJmfr@basile.remlab.net> (raw)
In-Reply-To: <20240226224438.1793-2-michael@niedermayer.cc>
Le tiistaina 27. helmikuuta 2024, 0.44.37 EET Michael Niedermayer a écrit :
> Signed-off-by: Michael Niedermayer <michael@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/
_______________________________________________
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-03-03 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 22:44 [FFmpeg-devel] [PATCH 1/3] doc/community: Vote in the interest of the project (first " Michael Niedermayer
2024-02-26 22:44 ` [FFmpeg-devel] [PATCH 2/3] doc/community: Conflict of interest recusal requirement (Similar to mid " Michael Niedermayer
2024-03-03 8:19 ` Rémi Denis-Courmont [this message]
2024-03-04 0:46 ` Michael Niedermayer
2024-03-04 9:42 ` Vittorio Giovara
2024-03-05 2:06 ` Michael Niedermayer
2024-02-26 22:44 ` [FFmpeg-devel] [PATCH 3/3] doc/community: presumed conflict of interest (similar to antons last part of his proposal) Michael Niedermayer
2024-03-03 2:53 ` [FFmpeg-devel] [PATCH 1/3] doc/community: Vote in the interest of the project (first part of Antons proposal) Michael Niedermayer
2024-03-03 8:05 ` Rémi Denis-Courmont
2024-03-04 0:29 ` Michael Niedermayer
2024-03-03 8:19 ` Andreas Rheinhardt
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=5680631.yRUoJKJmfr@basile.remlab.net \
--to=remi@remlab.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