From: Dave Taht <dave.taht@gmail.com>
To: Tech Board Discuss <tech-board-discuss@lists.linux-foundation.org>
Subject: [Tech-board-discuss] TAB nomination for Dave Taht
Date: Wed, 26 Oct 2016 11:53:44 -0700 [thread overview]
Message-ID: <CAA93jw4jbzV=HyjV+rM365=VX-F6S2NTr4jr8Fj-bC7p78XSCQ@mail.gmail.com> (raw)
I'm standing for election to the Technical Advisory Board.
I have been working on, in, and around Linux since 1993, and have been
deeply involved in the embedded Linux ecosystem since 1998. I run the
bufferbloat project[1], which is trying to eliminate network latency
from everything, with much of the work designed for and landing in
Linux. Most of my efforts in the past year have been around finding
ways to make wifi scale up to the new demands placed on it, in the
make-wifi-fast project[2]. I also work with the IETF aqm/babel and
IEEE 802.11 working groups, and last year spearheaded a campaign
explaining a few complex issues about embedded software to government
agencies like the FCC[3].
My purpose in running for the TAB is to A) facilitate better
communications about the real problems technically, organizationally,
and politically, in a rapidly changing, and often terrifying, world of
ever more computers everywhere, and B) to help try to develop coherent
responses and long term development, support and plans sufficient for
bringing Spaceship Earth in for a safe landing.
Jim Gettys and I saw the oncoming headlights of the embedded IoT
disaster many years ago[4], and have been working to fix it ever
since.
[1] https://www.bufferbloat.net
[2] https://www.bufferbloat.net/projects/make-wifi-fast/wiki/
[3] http://www.computerworld.com/article/2993112/security/vint-cerf-and-260-experts-give-fcc-a-plan-to-secure-wi-fi-routers.html
[4] https://www.bufferbloat.net/projects/make-wifi-fast/wiki/Solving_the_Home_Router_Disaster_Annotated/
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
reply other threads:[~2016-10-26 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw4jbzV=HyjV+rM365=VX-F6S2NTr4jr8Fj-bC7p78XSCQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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).