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 ESMTPS id 1896E48A0F for ; Mon, 20 Jan 2025 18:14:56 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 2DF4E68A79A; Mon, 20 Jan 2025 20:14:53 +0200 (EET) Received: from mout-p-101.mailbox.org (mout-p-101.mailbox.org [80.241.56.151]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id EB6AD6898FC for ; Mon, 20 Jan 2025 20:14:45 +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-101.mailbox.org (Postfix) with ESMTPS id 4YcJQW3WGMz9sZZ for ; Mon, 20 Jan 2025 19:14:43 +0100 (CET) Message-ID: <4f72a0e8-d5f2-4796-8376-aa5790f2bd97@gyani.pro> Date: Mon, 20 Jan 2025 23:44:41 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20250102141731.GR4991@pb2> Content-Language: en-US From: Gyan Doshi In-Reply-To: X-Rspamd-Queue-Id: 4YcJQW3WGMz9sZZ X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [FFmpeg-devel] Democratization 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: On 2025-01-20 11:14 pm, Soft Works wrote: > - An indication that the aim and direction of the contribution is > generally acceptable This the crux of the matter. There appear to be two camps at odds with one another: 1) a conservative camp which wants to avoid features or changes which don't neatly fit within a conventional pure architecture with clear separation of roles and duties, or features which are of use only to some users and, 2) a broadband camp which accepts features which are niche or which require some hybrid accommodation in its implementation. For most of ffmpeg history, the latter has been the dominant camp. But not in recent history. Tweaking the structures or procedures of governance can't ultimately bridge this chasm. It's almost like these camps should be part of different projects. Regards, Gyan _______________________________________________ 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".