* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
@ 2025-09-03 14:58 ` Donald Zickus
[not found] ` <270ee39772be4b268952f764e54e2c9b@ti.com>
2025-09-04 15:35 ` Greg KH
` (6 subsequent siblings)
7 siblings, 1 reply; 15+ messages in thread
From: Donald Zickus @ 2025-09-03 14:58 UTC (permalink / raw)
To: kernelci; +Cc: Gustavo Padovan, mwaqar
Hi,
On Tue, Sep 2, 2025 at 3:24 PM Donald Zickus <dzickus@redhat.com> wrote:
>
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
I forgot to add, we would like to finalize the nominations by Friday
September 12th.
Cheers,
Don
>
> Cheers,
> Don Zickus - Chair KernelCI Board
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
2025-09-03 14:58 ` Donald Zickus
@ 2025-09-04 15:35 ` Greg KH
2025-09-06 19:36 ` Greg KH
2025-09-04 15:47 ` Mark Brown
` (5 subsequent siblings)
7 siblings, 1 reply; 15+ messages in thread
From: Greg KH @ 2025-09-04 15:35 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, Gustavo Padovan, mwaqar
On Tue, Sep 02, 2025 at 03:24:13PM -0400, Donald Zickus wrote:
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
I would like to nominate myself.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-04 15:35 ` Greg KH
@ 2025-09-06 19:36 ` Greg KH
0 siblings, 0 replies; 15+ messages in thread
From: Greg KH @ 2025-09-06 19:36 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, Gustavo Padovan, mwaqar
On Thu, Sep 04, 2025 at 05:35:22PM +0200, Greg KH wrote:
> On Tue, Sep 02, 2025 at 03:24:13PM -0400, Donald Zickus wrote:
> > (resending text/plain)
> >
> > Hello KernelCI community!
> >
> > We have recently revised the KernelCI TSC charter[0] to establish a
> > more effective approach for our future work. The TSC will continue to
> > monitor and provide technical direction for all activities and
> > services related to KernelCI. Additionally, with the inception of the
> > Infrastructure Working Group, the TSC will serve as the primary
> > interface between the KernelCI community and our key users (kernel
> > maintainers and developers, hardware/cloud vendors, etc.), translating
> > user needs to the Infrastructure WG.
> >
> > The updated charter requires a new committee to be elected, consisting
> > of no more than four members, each serving a one-year term, with only
> > one member per company.
> >
> > If you would like to nominate yourself for a committee position on the
> > TSC, please reply to this email with your nomination request.
>
> I would like to nominate myself.
As for an introduction:
I am only a kernel developer and maintainer, I do not work on
kernelci, but I want to rely on it for my development efforts for both
patch review of stuff submitted to my subsystem, as well as the stable
kernel releases. Kernel developers shouldn't be getting multiple
emails from different CI systems, we should only need 1 common place
for this work to happen, and that's what I want to help make kernelci
become.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
2025-09-03 14:58 ` Donald Zickus
2025-09-04 15:35 ` Greg KH
@ 2025-09-04 15:47 ` Mark Brown
2025-09-04 17:03 ` Arisu Tachibana
` (4 subsequent siblings)
7 siblings, 0 replies; 15+ messages in thread
From: Mark Brown @ 2025-09-04 15:47 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, Gustavo Padovan, mwaqar
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
On Tue, Sep 02, 2025 at 03:24:13PM -0400, Donald Zickus wrote:
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
I'd like to nominate myself (thanks for the reminder Greg!).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
` (2 preceding siblings ...)
2025-09-04 15:47 ` Mark Brown
@ 2025-09-04 17:03 ` Arisu Tachibana
2025-09-04 18:26 ` Gustavo Padovan
` (3 subsequent siblings)
7 siblings, 0 replies; 15+ messages in thread
From: Arisu Tachibana @ 2025-09-04 17:03 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, Gustavo Padovan, mwaqar
On Wed, Sep 3, 2025 at 4:24 AM Donald Zickus <dzickus@redhat.com> wrote:
>
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
>
I would like to nominate myself.
thanks,
arisut
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
` (3 preceding siblings ...)
2025-09-04 17:03 ` Arisu Tachibana
@ 2025-09-04 18:26 ` Gustavo Padovan
2025-09-05 7:27 ` Guillaume Tucker
` (2 subsequent siblings)
7 siblings, 0 replies; 15+ messages in thread
From: Gustavo Padovan @ 2025-09-04 18:26 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, mwaqar
Hello,
---- On Tue, 02 Sep 2025 16:24:13 -0300 Donald Zickus <dzickus@redhat.com> wrote ---
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
I am adding my nomination too to run the elections for a TSC seat.
In the past two years, I have been heavily involved in the strategic directions
and technical architecture of KernelCI. During this time I have been representing
the project in various conferences and community meetings. I am also a
contributor to several projects in our github codebase.
Best,
- Gus
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
` (4 preceding siblings ...)
2025-09-04 18:26 ` Gustavo Padovan
@ 2025-09-05 7:27 ` Guillaume Tucker
2025-09-06 12:09 ` Guillaume Tucker
2025-09-05 17:29 ` Yogesh Lal
2025-09-05 17:50 ` Donald Zickus
7 siblings, 1 reply; 15+ messages in thread
From: Guillaume Tucker @ 2025-09-05 7:27 UTC (permalink / raw)
To: Donald Zickus, kernelci; +Cc: Gustavo Padovan, mwaqar
Hi Don,
On 02/09/2025 9:24 pm, Donald Zickus wrote:
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
It looks like the link to the charter is missing.
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
Thank you, I would like to nominate myself.
Best wishes,
Guillaume
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-05 7:27 ` Guillaume Tucker
@ 2025-09-06 12:09 ` Guillaume Tucker
0 siblings, 0 replies; 15+ messages in thread
From: Guillaume Tucker @ 2025-09-06 12:09 UTC (permalink / raw)
To: Donald Zickus, kernelci; +Cc: Gustavo Padovan, mwaqar
Hello,
On 05/09/2025 9:27 am, Guillaume Tucker wrote:
> Hi Don,
>
> On 02/09/2025 9:24 pm, Donald Zickus wrote:
>> (resending text/plain)
>>
>> Hello KernelCI community!
>>
>> We have recently revised the KernelCI TSC charter[0] to establish a
>
> It looks like the link to the charter is missing.
>
>> more effective approach for our future work. The TSC will continue to
>> monitor and provide technical direction for all activities and
>> services related to KernelCI. Additionally, with the inception of the
>> Infrastructure Working Group, the TSC will serve as the primary
>> interface between the KernelCI community and our key users (kernel
>> maintainers and developers, hardware/cloud vendors, etc.), translating
>> user needs to the Infrastructure WG.
>>
>> The updated charter requires a new committee to be elected, consisting
>> of no more than four members, each serving a one-year term, with only
>> one member per company.
>>
>> If you would like to nominate yourself for a committee position on the
>> TSC, please reply to this email with your nomination request.
>
> Thank you, I would like to nominate myself.
My first contribution to KernelCI was the automated bisection tool in
2017, followed by the blueprints for the new API (now called Maestro)
and more advanced bisection at LPC 2019 before focusing on Chromebook
enablement at every level, from Depthcharge to a scalable LAVA lab
with a dedicated instance running Chrome OS user-space. In parallel,
I was the initial TSC chair and then Board chair from 2020 to 2023
during which time I initiated the Sysadmin WG (now Infrastructure),
the community survey, the new API roadmap as well as the RFP for the
new web dashboard. Since I stepped down in early 2024, the KernelCI
team has been through a healthy renewal while I pursued my own path
and worked on a fork of the API called Renelick with several
use-cases related to automated kernel testing in the continuation of
my earlier work.
As of today, I can dedicate some time to contribute relevant
experience from an independent point of view and also expand the
outreach of the project via my growing involvement with the LF Energy
community since Linux is also present in electrical grids.
Best wishes,
Guillaume
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
` (5 preceding siblings ...)
2025-09-05 7:27 ` Guillaume Tucker
@ 2025-09-05 17:29 ` Yogesh Lal
2025-09-05 17:50 ` Donald Zickus
7 siblings, 0 replies; 15+ messages in thread
From: Yogesh Lal @ 2025-09-05 17:29 UTC (permalink / raw)
To: Donald Zickus; +Cc: kernelci, Gustavo Padovan, mwaqar, trilok.soni
On Wed, Sep 3, 2025 at 12:54 AM Donald Zickus <dzickus@redhat.com> wrote:
>
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
>
> Cheers,
> Don Zickus - Chair KernelCI Board
>
>
I would like to nominate for a TSC seat.
I am working with KernelCI community since a year now and actively
involved in bring up first external kernelci-labs( Qualcomm ) on
KernelCI2.0 model and since then maintaining Qualcomm kernelci-labs
and Qualcomm SoC platform on it.
Along with that I am working with the KernelCI community to streamline
kernelci-labs and integrate it to KernelCI.org and scale up the test
platform and plan to scale up the test coverage.
Also presented Qualcomm kernelci-labs integration with KernelCI.org at
Linaro Connect 2025
(https://resources.linaro.org/en/resource/tTW1et2jS2ivYxP2umR1d1) and
presented demo at Open Source Summit India, Hyderabad 2025.
Thanks and Regard
Yogesh Lal
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
` (6 preceding siblings ...)
2025-09-05 17:29 ` Yogesh Lal
@ 2025-09-05 17:50 ` Donald Zickus
2025-09-05 18:38 ` Mark Brown
2025-09-12 2:57 ` Arisu Tachibana
7 siblings, 2 replies; 15+ messages in thread
From: Donald Zickus @ 2025-09-05 17:50 UTC (permalink / raw)
To: kernelci
Cc: Gustavo Padovan, mwaqar, Hambardzumyan, Minas, Greg KH,
arisu.tachibana, broonie, Guillaume Tucker
Hi,
On Tue, Sep 2, 2025 at 3:24 PM Donald Zickus <dzickus@redhat.com> wrote:
>
> (resending text/plain)
>
> Hello KernelCI community!
>
> We have recently revised the KernelCI TSC charter[0] to establish a
> more effective approach for our future work. The TSC will continue to
> monitor and provide technical direction for all activities and
> services related to KernelCI. Additionally, with the inception of the
> Infrastructure Working Group, the TSC will serve as the primary
> interface between the KernelCI community and our key users (kernel
> maintainers and developers, hardware/cloud vendors, etc.), translating
> user needs to the Infrastructure WG.
>
> The updated charter requires a new committee to be elected, consisting
> of no more than four members, each serving a one-year term, with only
> one member per company.
>
> If you would like to nominate yourself for a committee position on the
> TSC, please reply to this email with your nomination request.
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.
Thanks!
Cheers,
Don
>
> Cheers,
> Don Zickus - Chair KernelCI Board
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: KernelCI TSC nomination request
2025-09-05 17:50 ` Donald Zickus
@ 2025-09-05 18:38 ` Mark Brown
2025-09-12 2:57 ` Arisu Tachibana
1 sibling, 0 replies; 15+ messages in thread
From: Mark Brown @ 2025-09-05 18:38 UTC (permalink / raw)
To: Donald Zickus
Cc: kernelci, Gustavo Padovan, mwaqar, Hambardzumyan, Minas, Greg KH,
arisu.tachibana, Guillaume Tucker
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Fri, Sep 05, 2025 at 01:50:23PM -0400, Donald Zickus wrote:
> 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've been involved in KernelCI for a long time, mainly as an upstream
kernel developer consuming the results and relatively small time lab
maintainer trying to get the best coverage out of the boards I have
available to me for the community. Most of what I've done with KernelCI
has been focused around making those two use cases better, plus some
marketing mostly to other kernel developers.
I'm also part of the team looking at the Arm internal KernelCI instance,
a key part of our CI strategy.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KernelCI TSC nomination request
2025-09-05 17:50 ` Donald Zickus
2025-09-05 18:38 ` Mark Brown
@ 2025-09-12 2:57 ` Arisu Tachibana
1 sibling, 0 replies; 15+ messages in thread
From: Arisu Tachibana @ 2025-09-12 2:57 UTC (permalink / raw)
To: Donald Zickus
Cc: kernelci, Gustavo Padovan, mwaqar, Hambardzumyan, Minas, Greg KH,
broonie, Guillaume Tucker
On Sat, Sep 6, 2025 at 2:50 AM Donald Zickus <dzickus@redhat.com> 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
^ permalink raw reply [flat|nested] 15+ messages in thread