lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161103164702.GB56112@clm-mbp>
Date:   Thu, 3 Nov 2016 10:47:03 -0600
From:   Chris Mason <clm@...com>
To:     Laurent Pinchart <laurent.pinchart@...asonboard.com>
CC:     <ksummit-discuss@...ts.linuxfoundation.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] Results: Linux Foundation Technical Advisory
 Board Election 2016

On Thu, Nov 03, 2016 at 06:06:35PM +0200, Laurent Pinchart wrote:
>Hi Steven,
>
>On Thursday 03 Nov 2016 11:39:51 Steven Rostedt wrote:
>> The TAB elections are now complete. Thank you to all the candidates for
>> putting their names forward, and a big thank you to Grant Likely, Shuah
>> Khan, Jes Sorensen, H. Peter Anvin, Chris Mason and the Linux Foundation
>> staff who helped handle the election logistics.
>>
>> With 108 ballots cast, the top 5 candidates received:
>>
>> The next highest voted candidate received 44 votes.
>>
>> Full results are available on request.
>
>Just curious, is there any particular reason to not publish the full results ?
>
>Could you also share feedback on the automated ballot counting process 

Just nominating yourself and going through an election can be 
uncomfortable, at least it always is for me.  We are lucky to have a 
deeply qualified group, and I'd rather focus on encouraging people that didn't 
get elected this time to try again next year.

The ballots were counted by hand.  Grant, Steve and Shuah each counted 
every ballot and they verified that everyone got the same results.

We also test drove the optical scanning of the ballots with a tool 
called SDAPS (http://sdaps.org).  This was Peter's idea, and it ended up 
working very nicely.

Out of 108 ballots, sdaps missed a single vote and didn't have any false 
positives.  The optical scanning was faster than the hand counting, and 
we used the SDAPS gui to verify each ballot, and correct the single 
miss.  The gui is the major reason I trusted the result, it's minimal 
but really fast.  We used an off-the-shelf scanner, chosen because it 
was the fastest model that fit in my suitcase.

SDAPS recommends latex to design the ballot, and provides macros to make 
it fairly painless.  Latex brings its own frustrations, but it worked.

-chris

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ