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 31595480C3 for ; Thu, 9 Nov 2023 18:50:26 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 877C768CB9D; Thu, 9 Nov 2023 20:50:24 +0200 (EET) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B7FC068C9B8 for ; Thu, 9 Nov 2023 20:50:17 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 0E43160006 for ; Thu, 9 Nov 2023 18:50:16 +0000 (UTC) Date: Thu, 9 Nov 2023 19:50:16 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231109185016.GE3543730@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> <169954957667.11195.13342031312073463508@lain.khirnov.net> <20231109173923.GA3543730@pb2> <169955354463.11195.2914048463799781240@lain.khirnov.net> MIME-Version: 1.0 In-Reply-To: <169955354463.11195.2914048463799781240@lain.khirnov.net> X-GND-Sasl: michael@niedermayer.cc 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: multipart/mixed; boundary="===============2742017397816468769==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2742017397816468769== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZbOrGex4OMgNghHz" Content-Disposition: inline --ZbOrGex4OMgNghHz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 09, 2023 at 07:12:24PM +0100, Anton Khirnov wrote: > Quoting Michael Niedermayer (2023-11-09 18:39:23) > > On Thu, Nov 09, 2023 at 06:06:16PM +0100, Anton Khirnov wrote: > > > 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 t= he same > > > > > as the GA from 2020, except for the extra members whose voting ri= ghts > > > > > expire after 2 years. > > > > >=20 > > > > > Do you dispute that?=20 > > > >=20 > > > > There are at least 3 issues here > > > >=20 > > > > * 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 rea= lly JB > > > > choose this list and also the one in 2020. Only he can explain wh= ere these > > > > lists come from and how they relate. > > >=20 > > > 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. > > >=20 > > > > * 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 t= old me. > > > > So even if you partially apply the rules these lists do not match > > >=20 > > > 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. > >=20 > > the 2020 GA list cannot have been created in July 2020 because there wh= ere > > votes prior that used it. >=20 > According to my mailbox, the vote on extra members was started on > 2020-06-18. TC/CC election vote was started on 2020-07-12. Zane had 29 > commits as of the former, and 30 as of the latter. In either case he > should have been on the list. >=20 > With what you told us so far, it is entirely possible he was on the > original list, but > * misremembered about not receiving the vote link, or > * did not get the email because of delivery issues (we had them even now > during the first attempt to initiate the vote). And thats why iam asking questions If jb says zane was on the original list, then * did the mail bounce / fail to deliver ? * did jb see that ? * there where 3 votes i would think it would be corrected after the fir= st bounce If jb says zane was not on the original list then thats what the current ev= idence suggests IMHO >=20 > > >=20 > > > > * The 2nd issue is that there are rules how to change the GA over t= ime > > > > like that after 2 years there needs to a confirmation AND that the > > > > other members represent the "active" developers in the last 36 mo= nths. > > > > I can see an argument to leave the 2020 GA untouched and use it a= s is > > > > I can also see an argument to update it, and exactly this was don= e in a > > > > vote in 2021 by JB. Now we are here trying the 3rd variant of app= lying > > > > 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, le= ts see > > > > where that might have come from .... > > >=20 > > > 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 ov= er > > > 2 years ago. What we are doing here is trying to clarify the rules so > > > that we actually can vote with some regularity. > >=20 > > Is it bikesheding if 2 lists that are supposed to be the same differ in > > multiple entries ? >=20 > It is the way you are doing it, with all these "just asking questions" > and vague accusations of impropriety. I have incomplete information so i need to ask questions. >=20 > > these are lists with roughly 50 entries, now we _know_ 2 people differ >=20 > We don't. You only mention one, whom I adress above. Who is the second? Alexander Strasser >=20 > > but there where 3 on the extra voters list so really 4 differ almost ce= rtainly >=20 > I do not understand this math. There where 3 extra developer voted onto the GA and there is zane. that makes 4 there is also Gautam Ramakrishnan on the posted list who simply did not have 20 commits at the time of the votes in 2020 thats 5. You cannot explain this away. Also Thilo mentioned that the number of voters was 49 without the 3 extra m= embers in the results while the list jb posted had 51 These things really dont match no matter how you turn it And again thats why iam asking questions. [...] > We don't need to "understand what happened", We do need to understand what happened. The whole project depends on the de= cissions of teh GA. This is not a joke, this is not something where we can be not su= re who was on the voter list thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I am the wisest man alive, for I know one thing, and that is that I know nothing. -- Socrates --ZbOrGex4OMgNghHz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZU0p5AAKCRBhHseHBAsP q2cQAJ0WZq92ddib9X69XBgdL/6ERPUPqQCcD+c+vKi6+pthGqHqm1FfJZRGrz4= =R/WF -----END PGP SIGNATURE----- --ZbOrGex4OMgNghHz-- --===============2742017397816468769== 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". --===============2742017397816468769==--