Re: KernelCI TSC nomination request

On Sat, Sep 6, 2025 at 2:50 AM Donald Zickus <[email protected]> wrote:
>
> Hi,


>
> Additional request, can folks add a small paragraph (2-3 sentences)
> about their involvement in kernelci that will be provided during
> voting.  I will poke current nominees next week if they haven't
> provided something by then.
> I will use the ones provided by Gustavo and Yogesh for theirs.
>

Hello everyone,

most of you already probably know me.
I'm Arisu Tachibana.
Current Gentoo Kernel project leader, GKernelCI creator, kci-dev
creator, CIP Kernel testing WG member and previous KernelCI TSC
member.
My view for KernelCI TSC as always been about improving collaboration
from Kernel developers/maintainers to KernelCI,
improving KernelCI workflow reflecting both personal necessity as
Gentoo Kernel sources maintainer but also about getting feedback from
Kernel and CIP SLTS kernel maintainers.
With the CIP kernel testing WG, I'm working adding and maintaining CIP
Kernel testing on KernelCI.
I first started creating OSS CI framework with GKernelCI (the CI that
is testing Gentoo Kernel Sources) and with GKernelCI starting to
collaborate with KernelCI.
GKernelCI was one of the first frameworks that got connected with
KCIDB to KernelCI.
With the previous KernelCI team we had a similar purpose but different
approach from how GKernelCI is working.
This different approach was one of the reason for creating kci-dev,
the command line tool for trigger checkout from KernelCI and check
results in formations.
kci-dev idea mostly come out from the possibility to add KernelCI
commands on my kernel development environment in a similar fashion of
what I'm doing with GkernelCI and gentoo-sources.

With my experience across multiple kernel testing initiatives and deep
understanding of maintainer workflows,
I'm committed to helping KernelCI evolve to meet the real-world needs
of our diverse kernel community.
I would be honored to serve on the TSC and contribute to KernelCI's
continued success.

Thanks,
Arisut