From: Kees Cook <keescook@google.com>
To: Tech Board Discuss <Tech-board-discuss@lists.linux-foundation.org>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] TAB nomination
Date: Wed, 7 Nov 2018 21:14:12 -0800 [thread overview]
Message-ID: <CAGXu5jKkip3aDzpH2ehuztdxm6_O9PuC1y2+uJckfLL1+tzt1w@mail.gmail.com> (raw)
Hi,
I'm volunteering to stand for election to the TAB.
My primary concern for the kernel is security. I've been a member of
the security@kernel.org response team for 5 years, and I've been
herding cats with the Kernel Self-Protection Project for 3 years. I
have frequently worked kernel-wide across many subsystems, or many
architectures, when helping landing 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 represent both of these concerns on the TAB.
In addition to being an active kernel developer and maintainer, 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 7 years.
I was a reluctant supporter of the Code of Conflict (it did not go far
enough), but I was even more unhappy with the sudden Code of Conduct
(due to lack of decision transparency and potential for very
counter-intuitive interpretations). I am, however, a fan of the base
intent and the recent clarifications: I've not enjoyed the times I've
been yelled at by Linus, and I have not liked seeing other toxic
interactions in the community. I'd like to help make sure the TAB
continues to support a positive social dynamic for contributors to the
kernel, stays up front about these kinds of changes going forward, and
that it is not unduly influenced by external forces.
Thanks for your consideration,
-Kees
--
Kees Cook
next reply other threads:[~2018-11-08 5:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 5:14 Kees Cook [this message]
2018-11-08 14:42 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 6:12 [Ksummit-discuss] " Andy Lutomirski
2018-11-13 6:58 ` Steven Rostedt
2018-11-13 7:09 ` Andy Lutomirski
2018-11-13 19:06 ` Chris Mason
2018-11-13 3:46 [Ksummit-discuss] TAB Nomination Mauro Carvalho Chehab
2018-11-13 4:31 ` Steven Rostedt
2018-11-13 4:48 ` Chris Mason
2018-11-12 20:09 [Ksummit-discuss] TAB nomination Laurent Pinchart
2018-11-10 20:52 [Ksummit-discuss] TAB Nomination Dan Williams
2018-11-10 18:44 Laura Abbott
2018-11-07 16:54 [Ksummit-discuss] TAB nomination Shuah Khan
[not found] <340499F8-3113-4C8E-946B-3C33A1C4E3A7@fb.com>
2018-11-06 23:42 ` Olof Johansson
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=CAGXu5jKkip3aDzpH2ehuztdxm6_O9PuC1y2+uJckfLL1+tzt1w@mail.gmail.com \
--to=keescook@google.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=ksummit-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