From: Dan Williams <dan.j.williams@intel.com>
To: tech-board-discuss@lists.linuxfoundation.org
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: [Ksummit-discuss] Self-nomination for 2020 TAB election
Date: Mon, 17 Aug 2020 13:10:56 -0700 [thread overview]
Message-ID: <CAPcyv4j5Cpo4F3VLOawK93BwtNXwMCi+4SNZEAQeV93T+BK9Wg@mail.gmail.com> (raw)
Hello,
Please add me to the candidate list for this year's TAB elections.
The Technical Advisory Board pools the experience and influence of a
group of Linux kernel development community members to collaborate and
respond to issues impacting the wider Linux community. I am motivated
to continue in this role, motivated to offer my perspective and effort
to positively impact the health of the community. In particular, I am
interested in the topics of maintainer-contributor relations,
inclusion, and the long term viability of the upstream / GPL Linux
kernel development model.
Since 2005 my kernel development experience has ranged from low-level
Arm / x86 enabling, to storage device-drivers, and most recently
persistent memory and device memory management. I believe I bring a
unique perspective to the TAB and am thankful for the opportunity to
serve with your support.
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next reply other threads:[~2020-08-17 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 20:10 Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-16 22:20 [Ksummit-discuss] Self-nomination for 2020 TAB election Laura Abbott
2020-08-16 20:49 Christian Brauner
2020-08-10 19:20 Kees Cook
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=CAPcyv4j5Cpo4F3VLOawK93BwtNXwMCi+4SNZEAQeV93T+BK9Wg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tech-board-discuss@lists.linuxfoundation.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).