tech-board-discuss.lists.linux.dev archive mirror
 help / color / mirror / Atom feed

From: Shuah <shuah@kernel.org>
To: tech-board-discuss@lists.linux.dev
Cc: shuah <shuah@kernel.org>, Shuah Khan <skhan@linuxfoundation.org>
Subject: Volunteering to serve on the Linux Technical Advisory Board
Date: Tue, 10 Sep 2024 11:11:17 -0600	[thread overview]
Message-ID: <4717b4ff-2f77-4240-908a-95129cc2a5bb@kernel.org> (raw)

All,

I am volunteering to serve on the Linux Technical Advisory Board.

I work across subsystems as a contributor and maintainer. I maintain
kselftest, USB over IP driver and tool, media vimc driver, and
cpupower tool. I co-maintain nolibc and kunit. My work requires me to
collaborate across the kernel subsystems and the community which is
challenging and fulfilling.

I serve on the Code of Conduct Committee focusing on making the
community a welcoming place for all. Serving on the CoC is
challenging. It requires making tough calls to investigate reports,
make decisions on the validity of the reports, and take action as
needed.

I serve on the Linux Plumbers Conference Program Committee to help run
the conference. LPC enables and fosters important discussions about
the kernel development connecting the kernel and user-space developer
communities.

I have designed and established mentorship program for new open source
developers. The mentorship program enables new developers from diverse
backgrounds to become productive members of open source communities.
I actively mentor many new kernel developers. This program has enabled
kernel experts to share their knowledge and train the next generation
of developers helping the community to sustain and thrive. Mentoring
keeps me actively engaged in understanding new developer experience
with the kernel community and the kernel development.

If elected, I would like to work with TAB focusing on the health of
the community and be a bridge to new developers, kernel community, and
the TAB.

Code of Conduct - https://www.kernel.org/code-of-conduct.html

thanks,
-- Shuah

                 reply	other threads:[~2024-09-10 17:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4717b4ff-2f77-4240-908a-95129cc2a5bb@kernel.org \
    --to=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tech-board-discuss@lists.linux.dev \
    /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

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).