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 354F949AEE for ; Sun, 3 Mar 2024 02:49:44 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6B68868D345; Sun, 3 Mar 2024 04:49:41 +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 A9F0168D32E for ; Sun, 3 Mar 2024 04:49:34 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 038A21C0002 for ; Sun, 3 Mar 2024 02:49:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1709434174; 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=otqYoMCAXxNJxR6sH5gsF0JILRyXwsSnzRe661+p3B4=; b=TlgpGsAjXo6cpAagthbsY5hjXaRQlI9XauSXQ2PTOXcNarWX6gQy2imLlLVQqLumCdXvZV igJXS750apNXF9RCYZhIOyJyCdWUeSBXx32jM686OjmDZJqCSByX0qM1kmEfPzBfebZrOJ ieHLOgY/gmFhg+V6hmkcVTOauyb5CQRHNJFlGEhcsCMu3SNML8a2JTRknLGbY9hmDpzSTe DV1sLyqnSFQ7MecoBKvR6erIMoBDv29lYzTUPDBQkltlHKBIDeufatMuODjemJcyl+cLFY GvG/Zu5wBKEXTEr9eOd5FWpfK8NdXwHi48uKhd8CvWTtVy3UXoVSsRDOz4sx1w== Date: Sun, 3 Mar 2024 03:49:33 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240303024933.GO6420@pb2> References: <170841737762.27417.14992162535824834057@lain.khirnov.net> <170931439255.29002.12138406678517187858@lain.khirnov.net> MIME-Version: 1.0 In-Reply-To: <170931439255.29002.12138406678517187858@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="===============9039034499153065420==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============9039034499153065420== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mojwtakxX99OTdgW" Content-Disposition: inline --mojwtakxX99OTdgW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Fri, Mar 01, 2024 at 06:33:12PM +0100, Anton Khirnov wrote: > Hi all, > it seems the discussion died down, There are patches pending, which i will apply soon if no objections have been raised. And noone owns law texts. Everyone can propose any derivation of anothers suggestion. Thats the idea behind evolution and improvment and the idea behind finding and dicussing variations. Depending on these patches outcome, i may propose options here That certainly does not qualify as "discussion died down" But as a precaution for the strange style of "quick vote before we find a consensus" Please add the vote options: (I belive this gives the people a more complete set of choices) * Wait for the discussion, consensus and patch based process to finish. After which, if disagreements remain, use the GA vote process. * Add a conflict of interrest text as specified by the patch below * Replace "If the disagreement involves a member of the TC, that member sho= uld recuse themselves from the decision." by the conflict of interrest text as specified by the patch below * Replace "If the disagreement involves a member of the TC, that member sho= uld recuse themselves from the decision." by "If the disagreement involves a member of the TC, that member mus= t recuse themselves from the decision." and add the conflict of interrest text as specified by the patch below * Replace "If the disagreement involves a member of the TC, that member sho= uld recuse themselves from the decision." by "If the disagreement involves a member of the TC, that member mus= t recuse themselves from the decision." (if the patch doesnt apply use best effort to merge manually) --- a/doc/community.texi +++ b/doc/community.texi @@ -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 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. As you can see we have so many options to consider, its better if we first go through normal discussions and consensus finding instead of initiating a= vote while patches are pending on the very text the vote is about thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. U= ser questions about the command line tools should be sent to the ffmpeg-user ML. And questions about how to use libav* should be sent to the libav-user ML. --mojwtakxX99OTdgW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZePlOQAKCRBhHseHBAsP q9nsAKCKWgvhig3KUGVoiFA2WxlnEOgedQCePMRmLmJZm+BO5Cyn4A38aAo5tIQ= =a57d -----END PGP SIGNATURE----- --mojwtakxX99OTdgW-- --===============9039034499153065420== 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". --===============9039034499153065420==--