From: Shuah Khan <shuah@kernel.org>
To: ksummit-discuss@lists.linux-foundation.org,
Tech-board-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] TAB nomination
Date: Wed, 7 Nov 2018 09:54:46 -0700 [thread overview]
Message-ID: <a5575542-5c01-b906-c6c3-6942fc5d961b@kernel.org> (raw)
Hi All,
As an active contributor and maintainer, I enjoy collaborating with talented
group of developers with diverse backgrounds and expertise. As a maintainer
and a developer, I have the responsibility to uphold the technical standards
to make the Linux kernel better in each release.
I started out as an independent contributor to the Android mainlining effort.
I maintain Kernel Selftest and USB over IP drivers. My role as a Kselftest
maintainer has overlaps with several critical kernel sub-systems and
continues to challenge me to be a good citizen of the community while
encouraging others to do the same.
During my previous tenure as a TAB member, I contributed to the Linux Kernel
Community Enforcement Statement work. It was behind the scenes work to explain
the need for the statement and get developers, maintainers and Corporate
members to lend their support. It was a very important effort for the
continued success of the Linux kernel in the industry as the platform for
open source eco-systems. I am proud to have played an important role in the
process.
It has been an eventful and challenging couple of months for the Linux
Community with the recent developments. The Code of Conduct introduction
and subsequent discussion shined a spotlight on the community.
I have been active and vocal in the efforts to initiate an open discussion
to review the Code of Conduct to evolve it to allay concerns from the
community. I strongly believe the CoC is a step in the right direction for
us as a community to continue to be a welcoming place while maintaining high
technical and code standards for acceptance.
I am running for TAB to continue the efforts to evolve the CoC process as
a member of the Technical Advisory board and work towards making the
community a welcoming place for a diverse group of developers.
I believe I can bring a unique perspective of women in the open source
community to the TAB. I hope I can count on your support to help represent
the community.
thanks,
-- Shuah
next reply other threads:[~2018-11-07 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:54 Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 6:12 [Ksummit-discuss] TAB nomination 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-08 5:14 [Ksummit-discuss] TAB nomination Kees Cook
[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=a5575542-5c01-b906-c6c3-6942fc5d961b@kernel.org \
--to=shuah@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).