[Members] voting results board and council elections
gnauck at gmail.com
Wed Nov 22 12:40:00 UTC 2017
I second Dave's proposal, its in line with RFC 3797 and our bylaws to
------ Original Message ------
From: "Dave Cridland" <dave at cridland.net>
To: "Alexander Gnauck" <gnauck at gmail.com>; "XSF Members"
<members at xmpp.org>
Sent: 22.11.2017 12:51:35
Subject: Re: [Members] voting results board and council elections
>On 22 November 2017 at 10:59, Alexander Gnauck <gnauck at gmail.com>
>>We will resolve the tie ASAP for the 5th board position between Arc
>>and Nicolas Vérité.
>>Recommendations for tie resolution according to RFC 3797 are welcome
>>this list or in the XSF MUC room.
>I think this is in line with RFC 3797:
>1) As random input source, I propose using the "Main Numbers" from the
>Euro Millions draw of next Friday, as announced here:
>2) Each number will be arranged in ascending order, separated by dots,
>and terminated by "./".
>3) The resultant string will be hashed according to SHA-256.
>4) The tied candidates will be arranged into alphabetic order (note,
>in this case this may be by first or last name, it makes no
>difference), to produce:
> Arc Riley
> Nicolas Vérité
>5) These will be numbered from 0. Thus Arc is denoted by 0, and Nÿco by
>6) The last bit of the hash (or, if you prefer, the value of the hash
>as a 256-bit string, modulo the length of the list) will then be used
>to select the candidate.
>As a worked example, if we take the results from yesterday:
>02 - 10 - 14 - 28 - 31
>We'd form the string "02.10.14.28.31./", which I can hash with:
>>>>h = hashlib.sha256('02.10.14.28.31./').hexdigest()
>Producing a hash (in hex) of
>This ending in a zero would result in Arc being selected.
>There is absolutely no way I or anyone else can predict or influence
>what this resolution will produce on Friday.
More information about the Members