public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Nikolai Kondrashov <spbnick@gmail.com>
To: "kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
	"kernelci-tsc@groups.io" <kernelci-tsc@groups.io>
Subject: New name for new "KernelCI"
Date: Thu, 23 May 2024 18:54:52 +0300	[thread overview]
Message-ID: <b51eab8a-41cd-4439-8434-076d09b60ed4@gmail.com> (raw)

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

             reply	other threads:[~2024-05-23 15:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 15:54 Nikolai Kondrashov [this message]
2024-05-23 17:10 ` New name for new "KernelCI" Trilok Soni
2024-05-23 17:12   ` Trilok Soni
2024-05-23 19:57   ` Gustavo Padovan
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=b51eab8a-41cd-4439-8434-076d09b60ed4@gmail.com \
    --to=spbnick@gmail.com \
    --cc=kernelci-tsc@groups.io \
    --cc=kernelci@lists.linux.dev \
    /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