Re: New name for new "KernelCI"
Guillaume Tucker <[email protected]>
| Newsgroups | dev.linux.lists.kernelci |
|---|---|
| Organization | gtucker.io |
| Message-ID | <[email protected]> |
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