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 B6C88474DF for ; Thu, 9 Nov 2023 17:06:26 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 166AE68C99B; Thu, 9 Nov 2023 19:06:24 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9907D68C99B for ; Thu, 9 Nov 2023 19:06:17 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 626282404B1 for ; Thu, 9 Nov 2023 18:06:17 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavis, port 10024) with ESMTP id D_Jcof9EcUL8 for ; Thu, 9 Nov 2023 18:06:16 +0100 (CET) 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 CDBDB24043D for ; Thu, 9 Nov 2023 18:06:16 +0100 (CET) Received: by lain.khirnov.net (Postfix, from userid 1000) id AA37E1601B9; Thu, 9 Nov 2023 18:06:16 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <20231109162112.GX3543730@pb2> References: <169917627924.11195.16676364527851497705@lain.khirnov.net> <169952305288.11195.8661027913609939054@lain.khirnov.net> <20231109115525.GV3543730@pb2> <169953247356.11195.1507797262881301434@lain.khirnov.net> <20231109162112.GX3543730@pb2> Mail-Followup-To: FFmpeg development discussions and patches Date: Thu, 09 Nov 2023 18:06:16 +0100 Message-ID: <169954957667.11195.13342031312073463508@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA 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 Michael Niedermayer (2023-11-09 17:21:12) > On Thu, Nov 09, 2023 at 01:21:13PM +0100, Anton Khirnov wrote: > > As far as I can tell, the voter list in the last vote should be the same > > as the GA from 2020, except for the extra members whose voting rights > > expire after 2 years. > > > > Do you dispute that? > > There are at least 3 issues here > > * The first and maybe the biggest, is that our vote superviser can reply to > mails within 20min (like in this thread here) but is not replying to a simple > question within days where the list of voters comes from he used and how it > relates to the 2020 GA. It gives one the feeling he has some sort of > difficulty with awnsering that question > you took a guess here and replied, and i appreciate that. But really JB > choose this list and also the one in 2020. Only he can explain where these > lists come from and how they relate. JB did explain where the list comes from [1] - it was generated by the script that is now in our tree. Nobody disputed it in 2020. > * I know for a fact that at least zane was not in the 2020 GA as i talked > with him and i know he did cast a vote in 2023 because again he told me. > So even if you partially apply the rules these lists do not match Zane had 30 commits in July 2020, so he SHOULD have been on the list. If he wasn't, then it was a mistake in 2020. > * The 2nd issue is that there are rules how to change the GA over time > like that after 2 years there needs to a confirmation AND that the > other members represent the "active" developers in the last 36 months. > I can see an argument to leave the 2020 GA untouched and use it as is > I can also see an argument to update it, and exactly this was done in a > vote in 2021 by JB. Now we are here trying the 3rd variant of applying > only half the rules. > But whats more so, we actually are not. What you are doing here is > looking at what happened and trying to rationalize it, trying to find > an explanation for the list. Not stating upfront what this list is > IMO this is not acceptable for a vote. Uhm we found this list, lets see > where that might have come from .... To be honest, it very much seems to me that you are trying to bikeshed the process to death. Yes, it is imperfect, but that is to be expected given we've only used it a few times so far, and the last time was over 2 years ago. What we are doing here is trying to clarify the rules so that we actually can vote with some regularity. In the vote we just had, option A won its contests against B/C/D by 17/7, 23/1, and 17/7, respectively. While it is possible that the list used was not entirely correct (also depending on the intepretation of the rules), I see no reason to think it was incorrect in 10 people, which is what you'd need to have a chance of getting a different result. [1] http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2020-June/264732.html -- 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".