KernelCI discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Donald Zickus <dzickus@redhat.com>
Cc: kernelci <kernelci@lists.linux.dev>,
	Gustavo Padovan <gustavo.padovan@collabora.com>,
	mwaqar <mwaqar@linuxfoundation.org>
Subject: Re: KernelCI TSC nomination request
Date: Sat, 6 Sep 2025 21:36:37 +0200	[thread overview]
Message-ID: <2025090637-aversion-ninetieth-0481@gregkh> (raw)
In-Reply-To: <2025090409-regally-shock-45cc@gregkh>

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

  reply	other threads:[~2025-09-06 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 19:24 KernelCI TSC nomination request Donald Zickus
2025-09-03 14:58 ` Donald Zickus
     [not found]   ` <270ee39772be4b268952f764e54e2c9b@ti.com>
     [not found]     ` <CAK18DXZFbdh9+qX6e6onp1=S_GE_FybBVvo_JGO2rv_rEdGZ1g@mail.gmail.com>
2025-09-05 18:47       ` [EXTERNAL] " Minas Hambardzumyan
2025-09-08 13:39         ` Minas Hambardzumyan
2025-09-04 15:35 ` Greg KH
2025-09-06 19:36   ` Greg KH [this message]
2025-09-04 15:47 ` Mark Brown
2025-09-04 17:03 ` Arisu Tachibana
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
2025-09-05 18:38   ` Mark Brown
2025-09-12  2:57   ` 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=2025090637-aversion-ninetieth-0481@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dzickus@redhat.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=mwaqar@linuxfoundation.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