From: Nikolai Kondrashov <spbnick@gmail.com>
To: kernelci-tsc@groups.io,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: [kernelci-tsc] New name for new "KernelCI"
Date: Wed, 12 Jun 2024 16:56:23 +0200 [thread overview]
Message-ID: <7f9eca2b-e2e5-4288-a9c4-bd8be09f33fa@gmail.com> (raw)
In-Reply-To: <17D6135FD5E0FC8F.2477@groups.io>
[-- 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 --]
next prev parent reply other threads:[~2024-06-12 14:56 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
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 ` Nikolai Kondrashov [this message]
2024-06-12 17:27 ` [kernelci-tsc] " 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=7f9eca2b-e2e5-4288-a9c4-bd8be09f33fa@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