KernelCI discussions
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Guillaume Tucker <gtucker@gtucker.io>,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Cc: kernelci-members@groups.io, kernelci-tsc@groups.io,
	shuah <shuah@kernel.org>
Subject: Shuah Khan - Self nomination for KernelCI TSC Chair
Date: Wed, 14 Feb 2024 17:04:30 -0700	[thread overview]
Message-ID: <db438c3b-05d3-4c9c-9730-b99fec6b2ccf@linuxfoundation.org> (raw)

Hi,

I would like to submit my nomination for KernelCI TSC Chair.

https://lore.kernel.org/kernelci/260bfac4-0d48-2a10-e15d-75695ae12544@gtucker.io/

I am a Kernel Maintainer & Linux Fellow at The Linux Foundation.
I maintain Kselftest, KUnit, USBIP, vimc drivers, and cpupower
tool. I am an administrative co-maintainer for nolibc.

As a developer, maintainer, and contributor, I consider kernel
testing and validation are two very important aspects of the
development process. I am interested in seeing automated testing
and test rings succeed and thrive.

If elected, I would like to work towards continued success of
KernelCI.

Other hats I wear:
- Serve on the Linux kernel Code of Conduct committee.
- Authored A Beginner’s Guide to Linux Kernel Development (LFD103).
- Lead the Linux Foundation Mentorship program aimed at increasing
   diversity in open source and providing equitable access to learning
   resources.
- Served as the ELISA project TSC Chair and continue to contribute
   acting as a bridge between ELISA Safety and Linux kernel communities.

thanks,
-- Shuah


             reply	other threads:[~2024-02-15  0:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  0:04 Shuah Khan [this message]
2024-02-16 19:53 ` Shuah Khan - Self nomination for KernelCI TSC Chair Guillaume Tucker
2024-02-16 20:22   ` Shuah Khan
     [not found] ` <CAK18DXaOeQT1beoUOENtB94gX_Sr2AkbJD2kU7QkxE1RWGq9qA@mail.gmail.com>
2024-02-16 20:18   ` Shuah Khan
2024-02-20  4:48 ` Arisu Tachibana

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=db438c3b-05d3-4c9c-9730-b99fec6b2ccf@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=gtucker@gtucker.io \
    --cc=kernelci-members@groups.io \
    --cc=kernelci-tsc@groups.io \
    --cc=kernelci@lists.linux.dev \
    --cc=shuah@kernel.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