From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tech Board Discuss <Tech-board-discuss@lists.linux-foundation.org>
Cc: "ksummit-2010-discuss@lists.linux-foundation.org"
<ksummit-2010-discuss@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Fri, 15 Oct 2010 10:00:54 -0400 [thread overview]
Message-ID: <1287151254.3069.10.camel@mulgrave.site> (raw)
The elections for five of the ten members of the Linux Foundation
Technical Advisory Board[TAB] are held every year, currently the
election will be at the 2010 Kernel Summit in a BoF session on Tuesday
at Jillians (The Joint KS/Plumbers Reception on 2 November). The idea
is to be open to both KS and Plumbers attendees who wish to vote.
Anyone is eligible to stand for election, simply send your nomination
to:
Tech-board-discuss@lists.linux-foundation.org
We currently have two nominees (the incumbents):
James Bottomley <James.Bottomley@hansenpartnership.com>
Chris Mason <chris.mason@oracle.com>
The deadline for receiving nominations is up until the beginning of the
event where the election is held (on the Evening of 2 November Eastern
Time). Although, please remember if you're not going to be present that
things go wrong with both networks and mailing lists, so get your
nomination in early).
James Bottomley (TAB Chair)
next reply other threads:[~2010-10-15 14:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 14:00 James Bottomley [this message]
2010-10-15 17:18 ` [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process Chris Wright
2010-10-20 20:46 ` Daniel Walker
2010-11-02 21:36 ` Chris Wright
2010-10-20 18:02 ` Randy Dunlap
2010-10-20 20:42 ` Daniel Walker
2010-10-20 21:57 ` [Tech-board-discuss] [Ksummit-2010-discuss] " James Bottomley
2010-10-20 23:38 ` Randy Dunlap
2010-10-20 18:42 ` [Tech-board-discuss] " John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 20:28 [Tech-board-discuss] [Potential Spoof] [Tech-board] [draft v2] " Chris Mason
2016-10-14 20:34 ` [Tech-board-discuss] " Chris Mason
2015-10-06 10:06 Grant Likely
2015-10-06 14:21 ` Josh Triplett
2015-10-13 8:06 ` Grant Likely
2015-10-08 21:02 ` Shuah Khan
2015-10-13 8:08 ` Grant Likely
2015-10-11 4:20 ` Ric Wheeler
2015-10-13 8:12 ` Grant Likely
2015-10-13 13:09 ` Sage Weil
2015-10-14 17:48 ` Grant Likely
2015-10-13 5:19 ` Kees Cook
2015-10-13 8:10 ` Grant Likely
2015-10-20 0:54 ` Grant Likely
2015-10-20 12:39 ` Theodore Ts'o
2015-10-20 23:20 ` Grant Likely
2015-10-25 8:06 ` Grant Likely
2015-10-25 8:43 ` Grant Likely
2015-10-24 17:37 ` Olof Johansson
2014-07-15 21:48 James Bottomley
2014-08-18 20:13 ` James Bottomley
2014-08-19 14:43 ` Randy Dunlap
2014-08-19 19:03 ` James Bottomley
2014-08-19 3:03 ` Theodore Ts'o
2013-10-23 7:40 James Bottomley
2013-10-14 18:01 James Bottomley
2012-08-24 9:48 James Bottomley
2012-07-06 13:49 James Bottomley
2011-09-02 14:31 James Bottomley
2009-10-01 18:20 James Bottomley
2009-10-12 22:04 ` James Bottomley
2009-10-16 16:22 ` Grant Likely
2009-10-16 16:46 ` Roland Dreier
2009-10-16 17:06 ` David Woodhouse
2009-10-17 2:34 ` Thomas Gleixner
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=1287151254.3069.10.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--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).