New name for new "KernelCI"

New name for new "KernelCI"

[Nikolai Kondrashov]

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

RE: New name for new "KernelCI"

[Trilok Soni]

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.

---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

Re: New name for new "KernelCI"

[Trilok Soni]

On 5/23/2024 10:10 AM, Trilok Soni 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.

I have replied from my different email account so ignore the WARNINGs below. 

-- 
---Trilok Soni

RE: New name for new "KernelCI"

[Gustavo Padovan]

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
>

Re: New name for new "KernelCI"

[Kevin Hilman]

Nikolai Kondrashov <spbnick@gmail.com> writes:

[...]

> 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.

For these central software building blocks that coordinate much of what
happens, the image of the orchestra conductor definitely comes to mind,
so I think Maestro is perfect.

> 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),

Also the name of my local (Seattle) pro hockey team, so I like that one
too. :)

Kevin

RE: [kernelci-tsc] New name for new "KernelCI"

[Chris Paterson]

Hello Nickolai,

Thank you for kicking off this topic!

> From: kernelci-tsc@groups.io <kernelci-tsc@groups.io> On Behalf Of Nikolai
> Kondrashov via groups.io
> Sent: Thursday, May 23, 2024 4:55 PM
> 

[..]

> 
> 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
+1

> * KernelCI Needle (in a haystack) - focused, simple, powerful, experienced
> * KernelCI Nucleus - kernel-related, simple, powerful (when split)
+1
This also has good synergy with the KernelCI logo.

> * KernelCI PristineCI - simple, open
> * KernelCI Pulse - focused, simple, powerful, experienced
+0.5
Or perhaps "KernelCI Sense"
or "KernelCI Sensei" - it "teaches" us of issues.

> * KernelCI Tamanduá (anteater in Spanish) - bug-related, simple, focused
> * KernelCI Trails - focused, experienced, distributed
> * KernelCI Warden - focused, powerful, experienced, commanding
+1

Thanks, Chris

> 
> 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
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#969): https://groups.io/g/kernelci-tsc/message/969
> Mute This Topic: https://groups.io/mt/106265017/881120
> Group Owner: kernelci-tsc+owner@groups.io
> Unsubscribe: https://groups.io/g/kernelci-
> tsc/leave/11027977/881120/788298759/xyzzy [chris.paterson2@renesas.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

Re: New name for new "KernelCI"

[Nikolai Kondrashov]

On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
> 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>".

Almost two weeks have passed from my original message, and we have collected a
number of opinions and potential names. So I went ahead and created a poll to
help us pick the new name:

https://forms.gle/GY2uWw3yGLA6u5EbA

The poll requires authenticating to Google to limit the number of votes, but
if anyone has a problem with that, just post your response here (pick all the
options you like), and I'll add it myself. We'll close the poll in a week.

If you've already responded with your preferences on the maillists, and don't
want them changed, there's no need to vote again (although you can).

Our options (assume each is used with "KernelCI" in front):

Anthill
Arrow
Kraken
Lens
Lighthouse
Maestro
Needle
Nucleus
PristineCI
Pulse
Sense
Sensei
Tamanduá
Trails
Warden
Yuga


Thank you!
Nick

Re: New name for new "KernelCI"

[Guillaume Tucker]

On 05/06/2024 12:00, Nikolai Kondrashov wrote:
> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>> 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>".
> 
> Almost two weeks have passed from my original message, and we have collected a
> number of opinions and potential names. So I went ahead and created a poll to
> help us pick the new name:
> 
> https://forms.gle/GY2uWw3yGLA6u5EbA
> 
> The poll requires authenticating to Google to limit the number of votes, but
> if anyone has a problem with that, just post your response here (pick all the
> options you like), and I'll add it myself. We'll close the poll in a week.
> 
> If you've already responded with your preferences on the maillists, and don't
> want them changed, there's no need to vote again (although you can).
> 
> Our options (assume each is used with "KernelCI" in front):
> 
> Anthill
> Arrow
> Kraken
> Lens
> Lighthouse
> Maestro
> Needle
> Nucleus
> PristineCI
> Pulse
> Sense
> Sensei
> Tamanduá
> Trails
> Warden
> Yuga

Would this encompass KCIDB or would it remain a separate project?

Guillaume

Re: New name for new "KernelCI"

[Nikolai Kondrashov]

Hi Guillaume!

On 6/5/24 1:08 PM, Guillaume Tucker wrote:
> On 05/06/2024 12:00, Nikolai Kondrashov wrote:
>> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>>> 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>".
>>
> Would this encompass KCIDB or would it remain a separate project?

This would be just the KernelCI API/pipeline. I.e. there will be "KernelCI"
the project, then "KernelCI <Something>" the CI system, and "KernelCI KCIDB".

Nick

Re: [kernelci-tsc] New name for new "KernelCI"

[Nikolai Kondrashov]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>> 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>".
> 
> Almost two weeks have passed from my original message, and we have collected a
> number of opinions and potential names. So I went ahead and created a poll to
> help us pick the new name:
> 
> https://forms.gle/GY2uWw3yGLA6u5EbA
> 
> The poll requires authenticating to Google to limit the number of votes, but
> if anyone has a problem with that, just post your response here (pick all the
> options you like), and I'll add it myself. We'll close the poll in a week.

The week has passed, and the poll is now closed. We've collected ten
responses. An the clear winner is:

    "Maestro"

Thank you everyone!

The graph with the distribution of votes is attached.

Nick

[-- Attachment #2: votes.png --]
[-- Type: image/png, Size: 58604 bytes --]

Re: [kernelci-tsc] New name for new "KernelCI"

[Gustavo Padovan]

Hello,

On 6/12/24 11:56, Nikolai Kondrashov wrote:
> On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
>> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>>> 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>".
>> Almost two weeks have passed from my original message, and we have collected a
>> number of opinions and potential names. So I went ahead and created a poll to
>> help us pick the new name:
>>
>> https://forms.gle/GY2uWw3yGLA6u5EbA
>>
>> The poll requires authenticating to Google to limit the number of votes, but
>> if anyone has a problem with that, just post your response here (pick all the
>> options you like), and I'll add it myself. We'll close the poll in a week.
> The week has passed, and the poll is now closed. We've collected ten
> responses. An the clear winner is:
>
>      "Maestro"

Nice. So here comes Maestro!  This is a great step to clarify the new 
architecture.
We should first patch that in the documentation together with the 
overdue update
on the overall KernelCI architecture. I can look into a patch for that 
next week.

Now, when it comes to actually renaming the git repos and other things 
we want
to evaluate a proposal to bring kernelci-core, kernelci-api and 
kernelci-pipeline into
a monorepo kci-maestro. But that would be post Plumbers possibly as our 
focus is
super sharper on showing the new KernelCI there.

I guess we should also start tagging the maestro data in KernelCI as 
'kci-maestro' or
something like that and not 'kernelci' anymore. Jeny, thoughts on this?

Best,

- Gus

-- 
Gustavo Padovan
Kernel Lead

Collabora Ltd.
Platinum Building, St John's Innovation Park
Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718

Re: [kernelci-tsc] New name for new "KernelCI"

[Nikolai Kondrashov]

On 6/12/24 7:27 PM, Gustavo Padovan wrote:
> 
> Hello,
> 
> On 6/12/24 11:56, Nikolai Kondrashov wrote:
>> On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
>>> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>>>> 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>".
>>> Almost two weeks have passed from my original message, and we have collected a
>>> number of opinions and potential names. So I went ahead and created a poll to
>>> help us pick the new name:
>>>
>>> https://forms.gle/GY2uWw3yGLA6u5EbA
>>>
>>> The poll requires authenticating to Google to limit the number of votes, but
>>> if anyone has a problem with that, just post your response here (pick all the
>>> options you like), and I'll add it myself. We'll close the poll in a week.
>> The week has passed, and the poll is now closed. We've collected ten
>> responses. An the clear winner is:
>>
>>      "Maestro"
> 
> Nice. So here comes Maestro!  This is a great step to clarify the new
> architecture.
> We should first patch that in the documentation together with the overdue update
> on the overall KernelCI architecture. I can look into a patch for that next week.
> 
> Now, when it comes to actually renaming the git repos and other things we want
> to evaluate a proposal to bring kernelci-core, kernelci-api and
> kernelci-pipeline into
> a monorepo kci-maestro. But that would be post Plumbers possibly as our focus is
> super sharper on showing the new KernelCI there.
> 
> I guess we should also start tagging the maestro data in KernelCI as
> 'kci-maestro' or
> something like that and not 'kernelci' anymore. Jeny, thoughts on this?

I'm happy that we got a name, and I quite like it too :D

Let's also go over all this in the weekly tomorrow, and on the TSC calls!

Regarding KCIDB, I think the origin should be simply "maestro", similar to
other origins (like "0day", "tuxsuite", and "cki", not like company names that
we also have).

Nick

Re: [kernelci-tsc] New name for new "KernelCI"

[Jeny Sheth]

Hello,


On 12/06/24 11:03 pm, Nikolai Kondrashov wrote:

> On 6/12/24 7:27 PM, Gustavo Padovan wrote:
>> Hello,
>>
>> On 6/12/24 11:56, Nikolai Kondrashov wrote:
>>> On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
>>>> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>>>>> 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>".
>>>> Almost two weeks have passed from my original message, and we have collected a
>>>> number of opinions and potential names. So I went ahead and created a poll to
>>>> help us pick the new name:
>>>>
>>>> https://forms.gle/GY2uWw3yGLA6u5EbA
>>>>
>>>> The poll requires authenticating to Google to limit the number of votes, but
>>>> if anyone has a problem with that, just post your response here (pick all the
>>>> options you like), and I'll add it myself. We'll close the poll in a week.
>>> The week has passed, and the poll is now closed. We've collected ten
>>> responses. An the clear winner is:
>>>
>>>       "Maestro"
That's nice and as expected.
>> Nice. So here comes Maestro!  This is a great step to clarify the new
>> architecture.
>> We should first patch that in the documentation together with the overdue update
>> on the overall KernelCI architecture. I can look into a patch for that next week.
Sounds good.
>> Now, when it comes to actually renaming the git repos and other things we want
>> to evaluate a proposal to bring kernelci-core, kernelci-api and
>> kernelci-pipeline into
>> a monorepo kci-maestro. But that would be post Plumbers possibly as our focus is
>> super sharper on showing the new KernelCI there.
Wouldn't that be complicated? That way we would be binding all the 3 repos
more closely instead of letting them work as separate entities. Maybe we can
consider renaming the repos to include "maestro" in it?
>> I guess we should also start tagging the maestro data in KernelCI as
>> 'kci-maestro' or
>> something like that and not 'kernelci' anymore. Jeny, thoughts on this?
> I'm happy that we got a name, and I quite like it too :D
>
> Let's also go over all this in the weekly tomorrow, and on the TSC calls!
>
> Regarding KCIDB, I think the origin should be simply "maestro", similar to
> other origins (like "0day", "tuxsuite", and "cki", not like company names that
> we also have).
"kci-meastro" looks more suitable to me than just "maestro" as that
mentions name of the CI system more precisely.
Any particular reason to drop "kci-" from the origin? @Nickolai

Thanks,
Jeny

Re: [kernelci-tsc] New name for new "KernelCI"

[Denys Fedoryshchenko]

On Wed, 2024-06-12 at 14:27 -0300, Gustavo Padovan wrote:
> 
> Hello,
> 
> On 6/12/24 11:56, Nikolai Kondrashov wrote:
> > On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
> > > On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
> > > > 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>".
> > > Almost two weeks have passed from my original message, and we
> > > have collected a
> > > number of opinions and potential names. So I went ahead and
> > > created a poll to
> > > help us pick the new name:
> > > 
> > > https://forms.gle/GY2uWw3yGLA6u5EbA
> > > 
> > > The poll requires authenticating to Google to limit the number of
> > > votes, but
> > > if anyone has a problem with that, just post your response here
> > > (pick all the
> > > options you like), and I'll add it myself. We'll close the poll
> > > in a week.
> > The week has passed, and the poll is now closed. We've collected
> > ten
> > responses. An the clear winner is:
> > 
> >      "Maestro"
> 
> Nice. So here comes Maestro!  This is a great step to clarify the new
> architecture.
> We should first patch that in the documentation together with the 
> overdue update
> on the overall KernelCI architecture. I can look into a patch for
> that 
> next week.
> 
> Now, when it comes to actually renaming the git repos and other
> things 
> we want
> to evaluate a proposal to bring kernelci-core, kernelci-api and 
> kernelci-pipeline into
> a monorepo kci-maestro. But that would be post Plumbers possibly as
> our 
> focus is
> super sharper on showing the new KernelCI there.
I believe renaming anything at this current moment would significantly
set us back. Additionally, until we eliminate the legacy systems,
renaming is technically unfeasible.

However, I would like to propose creating a new repository called kci-
maestro. This repository would consolidate various scattered components
of the project, such as new deployment scripts, maintenance tools, and
local development install scripts (currently residing in kernelci-
deploy and mixed with legacy items).

Rather than attempting to merge elements that cannot be easily
integrated, this new repository could serve as a true orchestrator for
all other components.
> 
> I guess we should also start tagging the maestro data in KernelCI as 
> 'kci-maestro' or
> something like that and not 'kernelci' anymore. Jeny, thoughts on
> this?
> 
> Best,
> 
> - Gus
> 

Re: [kernelci-tsc] New name for new "KernelCI"

[Gustavo Padovan]

On 6/13/24 03:05, Denys Fedoryshchenko via groups.io wrote:
> On Wed, 2024-06-12 at 14:27 -0300, Gustavo Padovan wrote:
>> Hello,
>>
>> On 6/12/24 11:56, Nikolai Kondrashov wrote:
>>> On 6/5/24 12:00 PM, Nikolai Kondrashov via groups.io wrote:
>>>> On 5/23/24 6:54 PM, Nikolai Kondrashov wrote:
>>>>> 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>".
>>>> Almost two weeks have passed from my original message, and we
>>>> have collected a
>>>> number of opinions and potential names. So I went ahead and
>>>> created a poll to
>>>> help us pick the new name:
>>>>
>>>> https://forms.gle/GY2uWw3yGLA6u5EbA
>>>>
>>>> The poll requires authenticating to Google to limit the number of
>>>> votes, but
>>>> if anyone has a problem with that, just post your response here
>>>> (pick all the
>>>> options you like), and I'll add it myself. We'll close the poll
>>>> in a week.
>>> The week has passed, and the poll is now closed. We've collected
>>> ten
>>> responses. An the clear winner is:
>>>
>>>       "Maestro"
>> Nice. So here comes Maestro!  This is a great step to clarify the new
>> architecture.
>> We should first patch that in the documentation together with the
>> overdue update
>> on the overall KernelCI architecture. I can look into a patch for
>> that
>> next week.
>>
>> Now, when it comes to actually renaming the git repos and other
>> things
>> we want
>> to evaluate a proposal to bring kernelci-core, kernelci-api and
>> kernelci-pipeline into
>> a monorepo kci-maestro. But that would be post Plumbers possibly as
>> our
>> focus is
>> super sharper on showing the new KernelCI there.
> I believe renaming anything at this current moment would significantly
> set us back. Additionally, until we eliminate the legacy systems,
> renaming is technically unfeasible.
>
> However, I would like to propose creating a new repository called kci-
> maestro. This repository would consolidate various scattered components
> of the project, such as new deployment scripts, maintenance tools, and
> local development install scripts (currently residing in kernelci-
> deploy and mixed with legacy items).
>
> Rather than attempting to merge elements that cannot be easily
> integrated, this new repository could serve as a true orchestrator for
> all other components.

That seems a great start! Thank you, Denys.

Best,

- Gus

-- 
Gustavo Padovan
Kernel Lead

Collabora Ltd.
Platinum Building, St John's Innovation Park
Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718