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 82F3D49850 for ; Tue, 20 Feb 2024 09:21:44 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 3164168D127; Tue, 20 Feb 2024 11:21:41 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2911568CEAB for ; Tue, 20 Feb 2024 11:21:35 +0200 (EET) Authentication-Results: mail0.khirnov.net; dkim=pass (2048-bit key; unprotected) header.d=khirnov.net header.i=@khirnov.net header.a=rsa-sha256 header.s=mail header.b=JNDTxPjQ; dkim-atps=neutral Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id D831A240DA9 for ; Tue, 20 Feb 2024 10:21:34 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavis, port 10024) with ESMTP id QNNh0qX254Xn for ; Tue, 20 Feb 2024 10:21:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=khirnov.net; s=mail; t=1708420892; bh=ZrxtJVw4MsiXbNUR1XEicmZH4q9bRTe5V7OEMJUQ27Y=; h=Subject:From:To:In-Reply-To:References:Date:From; b=JNDTxPjQj6aqMoB1yg4o6T2MVaQrm/teZvySZYvO0IlsSNML1zd82Kxpn8ECwyMUk xmAfwsjqG2PpoyVe28NVdDE0EAC9BQiSyocCbG8VgO4iuwSOs6/4EUjs8yeCfbWy/k yY7wRjij4rdgA72JSqXRel0TR2pkwqwg1qPRy25/QcaraJraseZCMLgDfQ5W3hFyon a/HsenErAgU1/opttBEBQMVyufBPkcfxGHxiGz5cG/CZ7lyWr/eUvJsVIA9izd/yPX RVi2MxKkPqUASXcyL3D/nrYaIxAVb6b6J/fcfxWskZ47adgqtCmaTQA4MMImQwzjI6 Z3hVws2qOPSHw== Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id EF206240177 for ; Tue, 20 Feb 2024 10:21:32 +0100 (CET) Received: by lain.khirnov.net (Postfix, from userid 1000) id C76A51601B9; Tue, 20 Feb 2024 10:21:32 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: References: <170841737762.27417.14992162535824834057@lain.khirnov.net> <170841903359.27417.409422117260058401@lain.khirnov.net> Mail-Followup-To: FFmpeg development discussions and patches Date: Tue, 20 Feb 2024 10:21:32 +0100 Message-ID: <170842089279.31318.2654441079015212247@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Quoting Marton Balint (2024-02-20 10:12:34) > We have no means to prove financial interest, because it is not public. We also have no means to prove that committee members are acting in the project's interest. E.g. if I had no qualms about being dishonest, I could always ask a friend to object to controversial patches in my place, so I wouldn't lose my vote, and nobody could prove it. In the end some things have to be taken on trust. > For practical reasons, using patch authorship is better. Or maybe a more > general solution against bias is somewhat increasing the number of people > in the TC, and removing this rule alltogether. I woould be concerned about making the TC too slow and unwieldy, it already takes a lot of effort to push any decisions through. Keep in mind that during all of its existence it only ever made two decisions, and one of them spent over a year in limbo. -- Anton Khirnov _______________________________________________ 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".