From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook via Tech-board-discuss
<tech-board-discuss@lists.linux-foundation.org>
Cc: ksummit-discuss@lists.linux-foundation.org,
Kees Cook <keescook@google.com>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] TAB nomination
Date: Thu, 8 Nov 2018 09:42:29 -0500 [thread overview]
Message-ID: <20181108094229.174aa2ac@gandalf.local.home> (raw)
In-Reply-To: <CAGXu5jKkip3aDzpH2ehuztdxm6_O9PuC1y2+uJckfLL1+tzt1w@mail.gmail.com>
On Wed, 7 Nov 2018 21:14:12 -0800
Kees Cook via Tech-board-discuss
<tech-board-discuss@lists.linux-foundation.org> wrote:
> 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,
>
Thanks Kees, I added you to the document.
-- Steve
next prev parent reply other threads:[~2018-11-08 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 5:14 [Ksummit-discuss] TAB nomination Kees Cook
2018-11-08 14:42 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 20:09 Laurent Pinchart
2018-11-12 20:36 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
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=20181108094229.174aa2ac@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=keescook@google.com \
--cc=ksummit-discuss@lists.linux-foundation.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).