From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id A4DF548CE1 for ; Fri, 23 Feb 2024 14:15:22 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 48E2968C5E7; Fri, 23 Feb 2024 16:15:19 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 6957A68C05A for ; Fri, 23 Feb 2024 16:15:12 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 41NEFBJd014832 for ; Fri, 23 Feb 2024 15:15:11 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id 7762429536; Fri, 23 Feb 2024 15:15:11 +0100 (CET) Date: Fri, 23 Feb 2024 15:15:11 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <170841737762.27417.14992162535824834057@lain.khirnov.net> <20240223140024.GF6420@pb2> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="9PUuqbloIJvV3qrL" Content-Disposition: inline In-Reply-To: <20240223140024.GF6420@pb2> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Fri, 23 Feb 2024 15:15:11 +0100 (CET) Subject: Re: [FFmpeg-devel] [RFC] clarifying the TC conflict of interest rule X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --9PUuqbloIJvV3qrL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Michael Niedermayer (12024-02-23): > Each option should provide a patch. Fine. But the wording can be discussed too. Regards, -- Nicolas George --9PUuqbloIJvV3qrL Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-doc-community-strengthen-TC-member-recusal-rule.patch" >From 7955ed2c1074f85f0f55a58072a8623c8ff4bf34 Mon Sep 17 00:00:00 2001 From: Nicolas George Date: Fri, 23 Feb 2024 15:12:51 +0100 Subject: [PATCH] doc/community: strengthen TC member recusal rule The role of the TC, like any body of this kind, is not only to *decide* but to *convince* the involved parties that the decision is *fair*. To achieve that goal, the rules must not only exclude real conflicts of interest but even the appearance of bias. Sitting on the TC is not a *right*, does not mean the member is *above* the other developers, but rather a *duty*. The TC has several members who take up the duty if one or more members are recused or recuse themselves. Therefore it is best for the trust in the system to exclude preventively all members of the TC who might exhibit a bias or the suspicion of a bias to let decide the members who clearly had no pre-conception on the issue, Signed-off-by: Nicolas George --- doc/community.texi | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/community.texi b/doc/community.texi index 90d2b6f366..31d3e21df6 100644 --- a/doc/community.texi +++ b/doc/community.texi @@ -82,7 +82,17 @@ The TC has 2 modes of operation: a RFC one and an internal one. If the TC thinks it needs the input from the larger community, the TC can call for a RFC. Else, it can decide by itself. -If the disagreement involves a member of the TC, that member should recuse themselves from the decision. +Any member of the TC who had a strong opinion on the question raised before it was raised should recuse themselves. + +In particular, must recuse themselves any member of the TC who: +- participated in the discussion (on the ML, on IRC or elsewhere) in a specific direction (minor comments and questions being acceptable); +- has a personal interest in the outcome; +- is, was recently or soon will be employed by an entity having a personal interest in the outcome or has any kind of hierarchical relationship with such entity. +Failure to do so would result, upon discovery, into the exclusion of all FFmpeg governance bodies, including the general assembly, for a duration of no less than five years. + +Additionally, any member of the general assembly can recuse any member of the TC without having to provide a reason. + +If the application of these rules result in all members of the TC recused or if the remaining members do not feel comfortable being too few, that means the project is in a crisis of trust that needs to be resolved by the general assembly. The decision to use a RFC process or an internal discussion is a discretionary decision of the TC. -- 2.43.0 --9PUuqbloIJvV3qrL Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --9PUuqbloIJvV3qrL--