From: "H. Peter Anvin" <hpa@zytor.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: tech-board-discuss@lists.linux-foundation.org,
"ksummit-discuss@lists.linux..."
<ksummit-discuss@lists.linuxfoundation.org>,
ksummit-pc@lists.linux-foundation.org
Subject: [Ksummit-discuss] TAB 2016 self-nomination for re-election
Date: Wed, 2 Nov 2016 15:12:30 -0600 [thread overview]
Message-ID: <35322fb6-59c1-f1b6-4547-ad957a6056c2@zytor.com> (raw)
In-Reply-To: <20161102203040.9A80BC00E5B@callcc.thunk.org>
Much delayed, here is my self-nomination statement for re-election to
the Linux Foundation Technical Advisory Board.
I first got involved with Linux in early 1992, and have been ever
since. I currently work for Intel as Senior Principal Engineer, and
have been for 8 years, working on the Linux kernel and on CPU
architecture; I have been co-maintainer of the "tip tree" and the x86
architecture for close to 10. I have implemented a number of
subsystems in both the kernel, userspace, and in the lower levels
(including the bootloader Syslinux.)
In my role at Intel I have made it part of my mission to interface with
CPU and firmware designers and architects to make hardware more
Linux-friendly.
In recent years, one of my missions have been to bridge the gap
between Linux developers, especially in the kernel, and (especially)
the developers of tools. As such, I have informally been acting a
kind of liason with the gcc and llvm communities , which seems to have
been part of why the friction in that interface has been reduced;
similar things apply to several other communities.
I am passionate about infrastructure, which I consider an oft
neglected aspect which imposes a chronic tax (technical debt) on
further development. I set up the original kernel.org in 1997, and have
worked with the Linux Foundation on a number of infrastructure-related
projects. I also implemented the system for handling the ballots for
this year's election (hence the delay in this statement ;)).
I have a tendency to overengineer, as I believe that doing things right
from the start allows things to be more easily generalized and have
wider applicability; this is in many ways the essence of Open Source to me.
I have been on the TAB for two years, and would like to continue.
-hpa
parent reply other threads:[~2016-11-02 21:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20161102203040.9A80BC00E5B@callcc.thunk.org>]
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=35322fb6-59c1-f1b6-4547-ad957a6056c2@zytor.com \
--to=hpa@zytor.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=ksummit-pc@lists.linux-foundation.org \
--cc=rostedt@goodmis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).