From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: tech-board-discuss@lists.linux-foundation.org,
Kernel Summit Discussions
<ksummit-discuss@lists.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board election results 2017
Date: Thu, 26 Oct 2017 01:14:21 +0300 [thread overview]
Message-ID: <2984302.a0WA3y5s5U@avalon> (raw)
In-Reply-To: <9779b6c3-acd6-10aa-b9ca-c024cd77a861@zytor.com>
Hello,
On Wednesday, 25 October 2017 19:47:10 EEST H. Peter Anvin wrote:
> The TAB elections are now complete. Thank you to all the candidates for
> putting their names forward.
>
> With 73 ballots cast, the top 5 candidates received:
>
> Steve Rostedt 58
> Jonathan Corbet 57
> Greg Kroah-Hartman 57
> Tim Bird 39
> Ted Ts'o 37
>
> It was a very close election, with the next candidate on the list
> receiving 36 votes.
Do we have a procedure in place in case the tie that we only avoided by one
vote would have happened ?
> Full results are available on request.
>
> This year the ballot counting was done automatically, with visual review
> of the scanned ballots v. the automatic results done by myself and Chris
> Mason.
>
> A big thank you to all the candidates, to everyone that voted, and
> congratulations to the top candidates.
>
> -hpa
>
> -------------------------------------------------------------------------
>
> For the curious, technical details:
>
> The ballots were produced and counted by SDAPS, an open-source project
> (http://www.sdaps.org/). A set of custom scripts were used to simplify
> the generation and counting of ballots specifically for the purpose of
> these elections; those scripts are available at:
>
> http://git.zytor.com/users/hpa/ballot.git
>
> Eventually I hope to clean up these scripts, generalize them for other
> voting methods, document them a little better, and formally release them
> as an election package, but for now they are relatively specific to the
> approval voting.
>
> SDAPS is a bit difficult to build, due to a very large number of
> dependencies, some of which aren't well documented. It would be a very
> nice thing if distros would consider packaging it, especially since it
> is a very useful package.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-10-25 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 16:47 H. Peter Anvin
2017-10-25 22:14 ` Laurent Pinchart [this message]
2017-10-26 0:23 ` H. Peter Anvin
2017-10-26 2:00 ` [Ksummit-discuss] [Tech-board-discuss] " Dave Taht
2017-10-26 7:25 ` [Ksummit-discuss] " Matthew Wilcox
2017-10-26 11:11 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
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=2984302.a0WA3y5s5U@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linux-foundation.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