From: Shuah Khan <skhan@linuxfoundation.org>
To: Donald Zickus <dzickus@redhat.com>
Cc: Guillaume Tucker <gtucker@gtucker.io>,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
kernelci-members@groups.io, kernelci-tsc@groups.io,
shuah <shuah@kernel.org>, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Shuah Khan - Self nomination for KernelCI TSC Chair
Date: Fri, 16 Feb 2024 13:18:18 -0700 [thread overview]
Message-ID: <7ad0a492-fdd9-4a33-b34e-04d4f71256a8@linuxfoundation.org> (raw)
In-Reply-To: <CAK18DXaOeQT1beoUOENtB94gX_Sr2AkbJD2kU7QkxE1RWGq9qA@mail.gmail.com>
Hi Don,
Yes you are correct. We have met before.
Congratulations on being selected as the chair of the LF KernelCI.
Scheduling a meeting sounds good.
thanks,
-- Shuah
On 2/16/24 10:57, Donald Zickus wrote:
> Hi Shuah,
>
> Thanks for volunteering!! My name is Don Zickus and I work for Red Hat. I believe we have met at LPC a few times. I was recently voted as chair of the LF KernelCI project and would like to welcome you! I believe Gustavo will help you navigate the TSC process.
>
> Perhaps the TSC could schedule a meeting to ask questions and gather an understanding of your views.
>
> Thanks again for volunteering!
>
> Cheers,
> Don
>
> On Wed, Feb 14, 2024 at 7:10 PM Shuah Khan <skhan@linuxfoundation.org <mailto:skhan@linuxfoundation.org>> wrote:
>
> Hi,
>
> I would like to submit my nomination for KernelCI TSC Chair.
>
> https://lore.kernel.org/kernelci/260bfac4-0d48-2a10-e15d-75695ae12544@gtucker.io/ <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
>
>
next prev parent reply other threads:[~2024-02-16 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 0:04 Shuah Khan - Self nomination for KernelCI TSC Chair Shuah Khan
2024-02-16 19:53 ` Guillaume Tucker
2024-02-16 20:22 ` Shuah Khan
[not found] ` <CAK18DXaOeQT1beoUOENtB94gX_Sr2AkbJD2kU7QkxE1RWGq9qA@mail.gmail.com>
2024-02-16 20:18 ` Shuah Khan [this message]
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=7ad0a492-fdd9-4a33-b34e-04d4f71256a8@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=dzickus@redhat.com \
--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