From: Chris Mason <clm@fb.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-kernel@vger.kernel.org, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Results: Linux Foundation Technical Advisory Board Election 2016
Date: Fri, 4 Nov 2016 06:46:29 -0600 [thread overview]
Message-ID: <20161104124627.GA59062@clm-mbp.thefacebook.com> (raw)
In-Reply-To: <5281625.rbgKeEiQ6A@avalon>
On Thu, Nov 03, 2016 at 08:38:44PM +0200, Laurent Pinchart wrote:
>Hi Chris,
>
>On Thursday 03 Nov 2016 10:47:03 Chris Mason wrote:
>> On Thu, Nov 03, 2016 at 06:06:35PM +0200, Laurent Pinchart wrote:
>> > 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. 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.
>
>If it wasn't clear from my e-mail, I have complete trust in the TAP to hand
>count the ballots. I was curious about how the SDAPS automated process worked
>out, thank you for providing feedback about it.
No problem, I couldn't remember if I'd mentioned the hand counting when
I talked about the scanner during the election, so I was mostly
clarifying for the list.
Thanks to everyone who stopped by to vote!
-chris
prev parent reply other threads:[~2016-11-04 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 15:39 [Ksummit-discuss] Results: Linux Foundation Technical Advisory Board Election 2016 Steven Rostedt
2016-11-03 16:06 ` Laurent Pinchart
2016-11-03 16:47 ` Chris Mason
2016-11-03 18:38 ` Laurent Pinchart
2016-11-04 12:46 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161104124627.GA59062@clm-mbp.thefacebook.com \
--to=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).