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: Reminder: Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Tue, 26 Oct 2010 23:51:17 -0500 [thread overview]
Message-ID: <1288155077.19649.356.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 five nominees:
James Bottomley <James.Bottomley@hansenpartnership.com>
Chris Mason <chris.mason@oracle.com>
Chris Wright <chrisw@sous-sol.org>
Grant Likely <grant.likely@secretlab.ca>
John W. Linville <linville@tuxdriver.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-27 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 4:51 James Bottomley [this message]
2010-10-31 13:13 ` Reminder: Linux Foundation Technical Advisory Board Elections and Nomination process Konrad Rzeszutek Wilk
2011-10-24 22:26 reminder: " James Bottomley
2016-10-24 15:47 Reminder: " Chris Mason
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=1288155077.19649.356.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 NNTP newsgroup(s).