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 CBF9148A16 for ; Sun, 24 Mar 2024 02:22:01 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 37C0468D371; Sun, 24 Mar 2024 04:21:58 +0200 (EET) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2CDF668D286 for ; Sun, 24 Mar 2024 04:21:52 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 7A6121C0002 for ; Sun, 24 Mar 2024 02:21:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1711246911; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8Lgo8m5UW0e1f9g9teyzrW25PitA5bDggzPKJItkyMo=; b=C7ZKTBK2PYAM0VGYoSjQWp8qHY9xXFr8d90fR4fqy3XsBOzGDH8MEWQk6pT2CxmPhoIc2P +Eb+XnVnXhr9sLx67gBEKPskL1kPNpZkVxC+QwEXbHb9KJmTJZVPYgriCSI7mFkZVTk/2N u4SbfAdr2AXR8ink2bDYiqkJgPna//3YfStl5r7i3SznAY55zyOu+t2xVuexBup1XKJgSe +P6LXpmEcmDqvmyb0QdG+57NtER4TapeEFldYm53Y/qBknnmHRR4HjGJ+zZcbJH8aIg1K5 oxpCxBwT8khmKJ2nF31uSqhz33VK7VDjrzP9IgDKRL3SiNENCtSBrWxnmr1GBg== Date: Sun, 24 Mar 2024 03:21:50 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240324022150.GG6420@pb2> References: <170841737762.27417.14992162535824834057@lain.khirnov.net> <170931439255.29002.12138406678517187858@lain.khirnov.net> <171111197597.7287.15050275581822945754@lain.khirnov.net> MIME-Version: 1.0 In-Reply-To: <171111197597.7287.15050275581822945754@lain.khirnov.net> X-GND-Sasl: michael@niedermayer.cc 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 Content-Type: multipart/mixed; boundary="===============0668809715560426072==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============0668809715560426072== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9wbK3K3NYHEG5M1T" Content-Disposition: inline --9wbK3K3NYHEG5M1T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 22, 2024 at 01:52:55PM +0100, Anton Khirnov wrote: > Michael, > following up on the previous discussion in this thread - if you, > personally, would like to vote for a different option than those > suggested so far, please propose one. The goal of the vote is to find the option which most people prefer. Not the option that I personally prefer. The winning options often are compromises that noone has as their favorite but the team as a whole prefers. You also added 3 options yourself, which i presume you dont all intend to vote for yourself > I am not going to add a large number of options that nobody actually > wants to vote for, as it imposes a burden on the voters who have to > carefully read and compare all the options. The intend of the vote here is to resolve a disagreement we have. Simply omiting opposing options is not how Democracy works You could discuss with others and try to find a smaller set of options that still represent all cases the team may want. I think the 2 main cases from the ones proposed by me are: (that is just my feeling and i cant read peoples minds and there may be other preferrances that should be represented) @@ -82,6 +82,14 @@ The TC has 2 modes of operation: a RFC one and an intern= al 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. +Each TC member must vote on such decision according to what is, in their v= iew, best for the project. + +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. + +A conflict of interest is presumed to occur when a TC member has a persona= l interest +(e.g. financial) in a specific outcome of the case that differs from what = is best for the project. + +If the disagreement involves a member of the TC, that member must recuse t= hemselves from the decision. -If the disagreement involves a member of the TC, that member should recuse= themselves from the decision. The decision to use a RFC process or an internal discussion is a discretio= nary decision of the TC. @@ -82,6 +82,13 @@ The TC has 2 modes of operation: a RFC one and an intern= al 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. +Each TC member must vote on such decision according to what is, in their v= iew, best for the project. + +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. + +A conflict of interest is presumed to occur when a TC member has a persona= l interest +(e.g. financial) in a specific outcome of the case that differs from what = is best for the project. + -If the disagreement involves a member of the TC, that member should recuse= themselves from the decision. The decision to use a RFC process or an internal discussion is a discretio= nary decision of the TC. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB it is not once nor twice but times without number that the same ideas make their appearance in the world. -- Aristotle --9wbK3K3NYHEG5M1T Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZf+OOwAKCRBhHseHBAsP qzzAAJ0SWT2OAuuUleUlF+CLg18gUv30hACfcWl3oCMjMJc27bt0msD1Ac9scR0= =T0ra -----END PGP SIGNATURE----- --9wbK3K3NYHEG5M1T-- --===============0668809715560426072== 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". --===============0668809715560426072==--