ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Tech Board Discuss
	<tech-board-discuss@lists.linux-foundation.org>,
	Kernel Summit Discussions
	<ksummit-discuss@lists.linux-foundation.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board election results 2017
Date: Wed, 25 Oct 2017 19:00:57 -0700	[thread overview]
Message-ID: <CAA93jw5rwU+qR4yAM9rZEtPTygOi0xceiqgcTz3Yoe8H6e-OUg@mail.gmail.com> (raw)
In-Reply-To: <dcabec8a-ed6c-bfb0-d601-1913f1e6ec8d@zytor.com>

On Wed, Oct 25, 2017 at 5:23 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 10/26/17 00:14, Laurent Pinchart wrote:
>>
>>> 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 ?
>>
>
> In that case thw winner(s) would be drawn randomly.  The scanning tool
> scripts actually assigns each candidate a tiebreaker number via
> /dev/urandom, but we have not yet decided if we would do that or, for
> example, a physical coin toss.

Once upon a time, Heinlein, it was, I think, suggested that a
candidate for office be
picked entirely randomly from the pool. The lottery concept - the idea
that if you ran,
you had a small chance of serving no matter the popular vote - encouraged
participation.

>
> We have had ties in the past, and had one this time too, but none that
> has ever crossed the cut line.
>
>         -hpa
>
> _______________________________________________
> Tech-board-discuss mailing list
> Tech-board-discuss@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/tech-board-discuss



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2017-10-26  2:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 16:47 [Ksummit-discuss] " H. Peter Anvin
2017-10-25 22:14 ` Laurent Pinchart
2017-10-26  0:23   ` H. Peter Anvin
2017-10-26  2:00     ` Dave Taht [this message]
2017-10-26  7:25 ` 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=CAA93jw5rwU+qR4yAM9rZEtPTygOi0xceiqgcTz3Yoe8H6e-OUg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=hpa@zytor.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