public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Gustavo Padovan" <gus@collabora.com>
To: "Trilok Soni" <tsoni@quicinc.com>
Cc: "Nikolai Kondrashov" <spbnick@gmail.com>,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
	"kernelci-tsc@groups.io" <kernelci-tsc@groups.io>
Subject: RE: New name for new "KernelCI"
Date: Thu, 23 May 2024 20:57:46 +0100	[thread overview]
Message-ID: <195626-664f9f80-23-758bf280@3007099> (raw)
In-Reply-To: <BY5PR02MB67543462B27CBA2C56BE5249B0F42@BY5PR02MB6754.namprd02.prod.outlook.com>

On Thursday, May 23, 2024 13:10 EDT, Trilok Soni <tsoni@quicinc.com> wrote:

> Nikolai,
> 
> How about Yuga? It means following. 
> 
> Yuga:
> Meaning: “Era” or “Age.”
> Attributes: Experienced (through time), powerful, and open.
> Context: Yuga represents cycles of time and evolution.

That's interesting. One thing that I have been saying a lot lately is that we have a kernel that is 33 years old already, so the KernelCI architecture we have been putting in place lately is to be a foundation of something that will last generations.

The thing we need to name sits at the center of that coordinating tests specs, triggers, running tests and facilitating the job for multiple CI systems to join the party.

Best

- Gus

> 
> ---Trilok Soni
> 
> -----Original Message-----
> From: Nikolai Kondrashov <spbnick@gmail.com> 
> Sent: Thursday, May 23, 2024 8:55 AM
> To: kernelci@lists.linux.dev; kernelci-tsc@groups.io
> Subject: New name for new "KernelCI"
> 
> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
> 
> Hi everyone,
> 
> As you know, we've been developing the new KernelCI API [1], and the kernelci-pipeline [2] based on it, for quite a while.
> 
> However, by now it seems that too many things are being called "KernelCI": the project, pieces of the old system, pieces of the new system. We would also like to give the name of KernelCI the project a wider scope than just a particular CI system, and accommodate more packages/projects under its name.
> 
> So we would like to propose to call the new system "KernelCI <Something>".
> 
> And this message is about that "<Something>".
> 
> I think it would be good to have the new name associate with one or more of the below qualities/functions (but feel free to dispute and extend this):
> 
> * focused
> * simple
> * powerful
> * experienced (as in arising from experience)
> * open
> * distributed
> * commanding (a fleet)
> * kernel-related
> * bug-related
> 
> One of the current working names, that Gustavo Padovan has proposed, is "Maestro". As in "KernelCI Maestro". It hits the following associations:
> focused, powerful, experienced, commanding.
> 
> As a joke and to come up with an example, I suggested "Kraken", that is "KernelCI Kraken", which hits these: powerful, experienced (it's old), simple (minded), focused (on sinking ships), distributed (it has tentacles),
> 
> Keeping things short, here are all the ideas so far, in alphabetic order:
> 
> * KernelCI Anthill - bug-related, distributed, commanding, focused
> * KernelCI Arrow - focused, simple, powerful
> * KernelCI Kraken - powerful, experienced, simple, focused, distributed
> * KernelCI Lens - focused, powerful, simple
> * KernelCI Lighthouse - focused, simple, powerful, commanding, experienced
> * KernelCI Maestro - focused, powerful, experienced, commanding
> * KernelCI Needle (in a haystack) - focused, simple, powerful, experienced
> * KernelCI Nucleus - kernel-related, simple, powerful (when split)
> * KernelCI PristineCI - simple, open
> * KernelCI Pulse - focused, simple, powerful, experienced
> * KernelCI Tamanduá (anteater in Spanish) - bug-related, simple, focused
> * KernelCI Trails - focused, experienced, distributed
> * KernelCI Warden - focused, powerful, experienced, commanding
> 
> I would appreciate any arguments and ideas about this. Once we have all the names we can think of, and strike out ones we definitely don't like, I'll create and post a poll here to pick one.
> 
> Thank you!
> 
> Nick
> TSC Chair
> 
> [1] https://github.com/kernelci/kernelci-api
> [2] https://github.com/kernelci/kernelci-pipeline
>


  parent reply	other threads:[~2024-05-23 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 15:54 New name for new "KernelCI" Nikolai Kondrashov
2024-05-23 17:10 ` Trilok Soni
2024-05-23 17:12   ` Trilok Soni
2024-05-23 19:57   ` Gustavo Padovan [this message]
2024-05-28 18:55 ` Kevin Hilman
2024-05-29 15:22 ` [kernelci-tsc] " Chris Paterson
2024-06-05 10:00 ` Nikolai Kondrashov
2024-06-05 10:08   ` Guillaume Tucker
2024-06-05 11:05     ` Nikolai Kondrashov
     [not found] ` <17D6135FD5E0FC8F.2477@groups.io>
2024-06-12 14:56   ` [kernelci-tsc] " Nikolai Kondrashov
2024-06-12 17:27     ` Gustavo Padovan
2024-06-12 17:33       ` Nikolai Kondrashov
2024-06-13  5:55         ` Jeny Sheth
2024-06-13  6:05       ` Denys Fedoryshchenko
2024-06-13 12:54         ` Gustavo Padovan

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=195626-664f9f80-23-758bf280@3007099 \
    --to=gus@collabora.com \
    --cc=kernelci-tsc@groups.io \
    --cc=kernelci@lists.linux.dev \
    --cc=spbnick@gmail.com \
    --cc=tsoni@quicinc.com \
    /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