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

Gustavo Padovan <[email protected]>
Newsgroups dev.linux.lists.kernelci
Message-ID <[email protected]>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.