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 9D40D425A3 for ; Sat, 18 Nov 2023 19:01:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7B7ED68CC90; Sat, 18 Nov 2023 21:01:53 +0200 (EET) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 713DC68CBF9 for ; Sat, 18 Nov 2023 21:01:47 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 973FEC0003 for ; Sat, 18 Nov 2023 19:01:46 +0000 (UTC) Date: Sat, 18 Nov 2023 20:01:45 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231118190145.GS3543730@pb2> MIME-Version: 1.0 X-GND-Sasl: michael@niedermayer.cc Subject: [FFmpeg-devel] Vote Investigation of "GA voters list updates E_029f7195fed7aadf" 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="===============5741035822626431567==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5741035822626431567== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CsaQibW1pmBnOBXZ" Content-Disposition: inline --CsaQibW1pmBnOBXZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all This are the results of my investigation of issues in "Poll: GA voters list= updates E_029f7195fed7aadf" This has been reviewed by Alexander and Anton and comments from them have b= een incorporated. It has also been shown to jb and Thilo at the same time as Alexander and An= ton, but no comments have been received. The "Recommended action section is mostly my recommendations but they too h= ave been adjusted based on comments. All names of people have been stripped after review but are available on re= quest for research purposes. Mistakes done: 1. the voter list in 2023 did not match the list used in 2020 nor 2021, the= exact reason is not known 1a. the 3 "extra members" where missing from the new list. It seems this wa= s unintended but later explained by partially applying the GA rules 1b. There was one developer who voted in 2023 but did not receive a mail in= 2020, it is unclear if he was on the 2020 list as i found 2 lists, one wit= h him and one without 1c. There was one developer who was on the 2023 list but was not eligible i= n 2020, his mail bounced and its unlikely he could vote. 1d. There was one developer who contacted the supervisor and asked why he d= id not receive a mail, the supervisor added him though he was not eligible = in 2020 1e. There was one developer who was on the 2023 list but was not eligible i= n 2020, his mail did not bounce and he likely could vote 2. Three people had multiple email addresses on the used list, the vote sup= ervisor had no way of knowing for certain if one, two or none of these addr= esses would produce bounces Also it was assumed that tokens from bounced emails would be inaccessibl= e. 2 of the 3 people had one address bounce the 3rd seems not to have had b= ounces 3. In addition to the bounces mentioned above, 2 more addresses produced bo= unces, these people where likely unable to vote. 4. The option to update before, was not well defined and could not have bee= n implemented had it won. 5. The mail account used reached a send limit (100), It is believed this di= d not affect anyone's ability to vote as the first 53 batch should not have= triggered this. But rather the repeated batch triggered it The send limit was 100 because the first payment for the mail.de account= was not received yet, it is 500 now Conclusion: It is unlikely the vote result is affected as it was not close. But these i= ssues must be resolved for future votes as they could affect votes when the= results are close. Recommended action: 1. Two people should replace a single vote supervisor, they should work tog= ether and cross check each others action. Similar to a pilot and co-pilot i= n an aircraft 2. The server should log email addresses, this will make future investigati= ons MUCH simple (done) 3. When the decision maker(s) have any doubt, action should be delayed, no = action should be rushed, its always better to wait a few days longer 4. Every step should be announced and the Community should have the chance = to verify and suggest amendments. 5. The implementability of all options should be thought through before sta= rting a vote with an option. 6. Maximal transparency should be attempted. Any issues occurring during a = vote should be published. 7. Before every new series of votes a test vote with the same set of voters= should be done 7a.In this test vote, if any addresses bounced and working addresses are kn= own then the bouncing addresses should be replaced by the working address. = Per person only one address may be used in a (non test) vote. 8. The vote supervisor and admin should clearly state before a vote that th= ey act in the best interest of FFmpeg, and have the time, will and ability = to do so. 9. The vote supervisor and admin must disclose any conflict of interest tha= t may apply to them. 10.Voters should always pair a random number with their ballot, write it do= wn and verify it afterwards. 11.The formalities and time frames regarding announcements and votes should= be written down. thx PS: If more anomalies are found then i may update this. (please contact me in case you stumble accoss any serious anomalies not listed above) --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Dictatorship: All citizens are under surveillance, all their steps and actions recorded, for the politicians to enforce control. Democracy: All politicians are under surveillance, all their steps and actions recorded, for the citizens to enforce control. --CsaQibW1pmBnOBXZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZVkKFgAKCRBhHseHBAsP q9SiAJ9fM7PO1waW8JyhPQ18inXYXQWGjgCeNdnohP/lEzJc0F4rWQnNakygid8= =ft3s -----END PGP SIGNATURE----- --CsaQibW1pmBnOBXZ-- --===============5741035822626431567== 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". --===============5741035822626431567==--