[Members] voting results board and council elections

Arc Riley arcriley at gmail.com
Fri Nov 24 22:33:16 UTC 2017


Tonight's results are announced: 19 - 24 - 28 - 30 - 50

>>> hashlib.sha256(b'19.24.28.30.50./').hexdigest()
'f2507b627edc74d540e7cb747138ed7ee8e19d4458f9db5bfd3a92b5c97a9541'

So it appears Nico has won the 5th slot.


On Thu, Nov 23, 2017 at 2:34 AM, Alexander Gnauck <alex at ag-software.de>
wrote:

> the ordering is in Dave's proposal:
>
>  0  Arc Riley
>  1 Nicolas Vérité
>
> Alex
>
> ------ Original Message ------
> From: "Ashley Ward" <ash.wardly at gmail.com>
> To: "XSF Members" <members at xmpp.org>
> Sent: 23.11.2017 11:25:28
> Subject: Re: [Members] voting results board and council elections
>
> I think we need a process to decide whether we order the names by first or
> last name...
>
> --
> Ash
>
> On 23 Nov 2017, at 10:23, Alexander Gnauck <alex at ag-software.de> wrote:
>
> Thanks Nÿco,
>
> I will execute the random selection then on the next Euro Millions draw
> which is this Friday, November 24th 2017.
>
> Alex
> ------ Original Message ------
> From: "Nicolas Vérité" <nicolas.verite at gmail.com>
> To: "XSF Members" <members at xmpp.org>
> Sent: 22.11.2017 22:57:28
> Subject: Re: [Members] voting results board and council elections
>
> This sounds fair, and I find it very funny.
> Good luck Arc! ;-)
>
>
> On Wed, Nov 22, 2017 at 12:51 PM, Dave Cridland <dave at cridland.net> wrote:
>
>> 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.
>>
>
>
>
> --
> Nicolas Vérité (Nÿco)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20171124/3d444598/attachment.html>


More information about the Members mailing list