From: Chris Wright <chrisw@sous-sol.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>,
"ksummit-2010-discuss@lists.linux-foundation.org"
<ksummit-2010-discuss@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections and Nomination process
Date: Tue, 2 Nov 2010 14:36:53 -0700 [thread overview]
Message-ID: <20101102213653.GA13824@sequoia.sous-sol.org> (raw)
In-Reply-To: <20101015171820.GA25455@sequoia.sous-sol.org>
* Chris Wright (chrisw@sous-sol.org) wrote:
> * James Bottomley (James.Bottomley@HansenPartnership.com) wrote:
> > We currently have two nominees (the incumbents):
> >
> > James Bottomley <James.Bottomley@hansenpartnership.com>
> > Chris Mason <chris.mason@oracle.com>
>
> Add another incumbent:
>
> Chris Wright <chrisw@sous-sol.org>
Since I can't make the reception...
My name is Chris Wright and I am standing for re-election as a member
of the Linux Foundation's Technical Advisory Board. I've been involved
with Linux kernel developement for over 10 years now, spanning areas of
security, Linux -stable tree, and virtualization. I currently represent
virtualization interests on the TAB.
I have advocated for and been involved with the TAB since its inception
roughly 5 years ago. I got involved out of an interest in ensuring
that the (at the time) OSDL's resources were put to more constructive
use for the Linux kernel community.
As a technical voice of reason, the TAB provides input to the Linux
Foundation to help guide its efforts. Over time, I believe the TAB has
helped the LF build more constructive communication between the different
communities it represents (developers, vendors, end users). As a member
of the TAB, I am often called upon to represent the community in LF events
(LinuxCon, Collaboration Summit, End User Summit). You'll typically find
me there leading discussions on virtualization and looking for ways to
improve the Linux in that context.
Thank you for giving me the opportunity to represent on the TAB since
it began. I'd be honored to continue.
thanks,
-chris
next prev parent reply other threads:[~2010-11-02 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 14:00 James Bottomley
2010-10-15 17:18 ` [Tech-board-discuss] " Chris Wright
2010-10-20 20:46 ` Daniel Walker
2010-11-02 21:36 ` Chris Wright [this message]
2010-10-20 18:02 ` Randy Dunlap
2010-10-20 20:42 ` Daniel Walker
2010-10-20 21:57 ` [Ksummit-2010-discuss] " James Bottomley
2010-10-20 23:38 ` Randy Dunlap
2010-10-20 18:42 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2015-10-06 10:06 Grant Likely
2015-10-06 14:21 ` [Tech-board-discuss] " Josh Triplett
2015-10-20 0:54 ` Grant Likely
2015-10-20 12:39 ` [Tech-board-discuss] " Theodore Ts'o
2014-07-15 21:48 James Bottomley
2014-08-18 20:13 ` James Bottomley
2014-08-19 19:03 ` [Tech-board-discuss] " James Bottomley
2012-08-24 9:48 James Bottomley
2011-09-02 14:31 James Bottomley
2009-10-01 18:20 James Bottomley
2009-10-12 22:04 ` [Tech-board-discuss] " James Bottomley
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=20101102213653.GA13824@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=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
Powered by JetHome