[Members] voting results board and council elections

Guus der Kinderen guus.der.kinderen at gmail.com
Wed Nov 22 12:43:34 UTC 2017


As I don't think any reasonable claim of bias or favoritism can be made
after using the above procedure, I'm perfectly happy with it.

 Guus

On 22 November 2017 at 13:40, Alexander Gnauck <gnauck at gmail.com> wrote:

> I second Dave's proposal, its in line with RFC 3797 and our bylaws to me.
>
> Alex
>
>
> ------ 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> wrote:
>>
>>> We will resolve the tie ASAP for the 5th board position between Arc Riley
>>> and Nicolas Vérité.
>>> Recommendations for tie resolution according to RFC 3797 are welcome
>>> here on
>>> 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:
>> https://www.euro-millions.com/results
>>
>> 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 1.
>>
>> 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
>> 'ad2edee63a88d7b4b6109944b5222a6cce1c3719ac4d41acd0dbf8287465ace0'
>>
>> 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.
>>
>> Dave.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20171122/35416eec/attachment.html>


More information about the Members mailing list