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 916A7488D8 for ; Fri, 22 Mar 2024 04:24:17 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id B766268D56B; Fri, 22 Mar 2024 06:24:13 +0200 (EET) Received: from mout-p-201.mailbox.org (mout-p-201.mailbox.org [80.241.56.171]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id DC14F68C1C2 for ; Fri, 22 Mar 2024 06:24:06 +0200 (EET) Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4V18NM47p9z9sS2 for ; Fri, 22 Mar 2024 05:24:03 +0100 (CET) Message-ID: <4ecac11c-76ae-4dbc-b1ac-96cf8baa3e8a@gyani.pro> Date: Fri, 22 Mar 2024 09:54:01 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20240303072225.4095-1-ffmpeg@gyani.pro> Content-Language: en-US From: Gyan Doshi In-Reply-To: <20240303072225.4095-1-ffmpeg@gyani.pro> X-Rspamd-Queue-Id: 4V18NM47p9z9sS2 Subject: Re: [FFmpeg-devel] [PATCH] doc/community: rule to avoid conflict of interest and prejudice in TC 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 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Ping. Anton announced to have a vote on 4th Mar for changing the rule [1]. That's long past. It is holding up the consideration of the matter I raised [2] to the TC. Regards, Gyan [1]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-March/322464.html [2]: https://ffmpeg.org/pipermail/ffmpeg-devel/2024-February/321564.html On 2024-03-03 12:52 pm, Gyan Doshi wrote: > --- > doc/community.texi | 15 ++++++++++++++- > 1 file changed, 14 insertions(+), 1 deletion(-) > > diff --git a/doc/community.texi b/doc/community.texi > index 90d2b6f366..8d5722bd7f 100644 > --- a/doc/community.texi > +++ b/doc/community.texi > @@ -82,7 +82,20 @@ 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 has > + > +@itemize @bullet > +@item > +had a major participation in the discussion or demonstrated a partisan disposition on a disputed matter at any public venue, or > +@item > +a material interest in the resolution of the dispute, either directly or via current or anticipated employment or consideration > +@end itemize > + > +should be recused from participation in the TC activities related to the concerned matter. > +This recusal may be effected either directly by the TC member, or failing which, by a vote of the > +Community Committee (CC) - the TC member must not participate in any such vote. Failure by the TC member > +to reveal any such involvement as described above, if judged intentional and material by the CC, shall > +result in exclusion of said member from all FFmpeg governance bodies for a period of no less than two years. > > The decision to use a RFC process or an internal discussion is a discretionary decision of the TC. > _______________________________________________ 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".