From: Kees Cook <keescook@chromium.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self-nomination for 2020 TAB election
Date: Mon, 10 Aug 2020 12:20:29 -0700 [thread overview]
Message-ID: <202008101110.E14843431@keescook> (raw)
Hi,
I'm volunteering again to stand for election to the Technical Advisory
Board.
My primary concern for the kernel is security. I've been a member of
the security@kernel.org response team for 7 years, and I've been
herding cats with the Kernel Self-Protection Project[0] for 5 years. I
have frequently worked kernel-wide across many subsystems (or many
architectures) when helping land various security defenses. This
cross-maintainer work is a unique social and technical challenge, and
the topic of "security" is a similarly wide and unique challenge. I'd
like to continue to represent both of these concerns on the TAB.
In addition to being an active kernel developer and maintainer[1], I also
bring several "downstream" perspectives on how the kernel is consumed.
I understand the concerns of a general purpose-distro, having worked
on Ubuntu for 5 years. More recently, I know the demands of special
purpose device vendors, having worked on Chrome OS, Brillo, and
Android over the last 9 years.
In the last 2 years on the TAB I've supported the move to expanding the
TAB voting to online participation, and more recently spent time trying to
focus[2] the discussion of inclusive language into something productive
where we could still actually make meaningful changes in existing
subsystems[3], upstream projects[4], and, obviously, Coding Style[5].
Thanks for your consideration,
-Kees
[0] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project
[1] https://lore.kernel.org/lkml/?q=f%3A%22Kees+Cook%22+s%3A%22GIT+PULL%22
[2] https://lore.kernel.org/netdev/202006091312.F91BB4E0CE@keescook/
[3] https://git.kernel.org/linus/8d87ae48ced2dffd5e7247d19eb4c88be6f1c6f1
[4] https://github.com/acpica/acpica/commit/660a40adae4e192a7559fcf3484ad46663971c5b
[5] https://git.kernel.org/linus/a5f526ecb075a08c4a082355020166c7fe13ae27
--
Kees Cook
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next reply other threads:[~2020-08-10 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 19:20 Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-16 20:49 [Ksummit-discuss] Self-nomination for 2020 TAB election Christian Brauner
2020-08-16 22:20 Laura Abbott
2020-08-17 20:10 Dan Williams
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=202008101110.E14843431@keescook \
--to=keescook@chromium.org \
--cc=ksummit-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).