Thank you JB and Yufei for all clarifications.
Let's consider this one as DECLINED.
I will start a new one with following the established rules.
On 18/10/2025 05:11, Jean-Baptiste Onofré wrote:
Either way is fine with me. Imho a complete new vote would be probably clearer.
Regards
JB
On Fri, Oct 17, 2025 at 8:17 PM Yufei Gu <[email protected]> wrote:
Just wanna check, do we continue using this thread for the rename vote or
close this one, and open another vote with clarification?
Yufei
On Thu, Oct 16, 2025 at 10:38 PM Jean-Baptiste Onofré <[email protected]>
wrote:
As discussed yesterday and just to remind the good practice:
1. A vote is not "always" required, lazy consensus can be used,
without a need for a vote
2. A vote is to answer a "closed" question, not choose between open a,
b, c. A vote should be yes for that, not for that.
3. A vote email should have [VOTE] in the subject (the case here), and
list +1/-1 with the meaning.
So, for this vote, it should be:
+1 (use the pypolaris as Polaris CLI package name)
0 (I don't care)
-1 (don't see pypolaris because ...)
I vote +1 (binding) here, with the comment that if CLI is embedded in
the Polaris distribution, pypolaris would sound like a weird name (but
we can change while assembling the binary distribution).
Regards
JB
On Wed, Oct 15, 2025 at 2:19 PM Artur Rakhmatulin
<[email protected]> wrote:
Hello everyone.
I would like to open a VOTE for using "pypolaris" as the name of the
Apache Polaris CLI tool that will be available after installing the
Apache Polaris python distribution.
```
pip install apache-polaris
pypolaris --help
```
Motivation:
-avoid collisions with the existing ./polaris executable in the Apache
Polaris project
-avoid name collisions with other tools not related to Apache Polaris
-ease of use
-Initial Issue - Package Python CLI tool in the binary distribution [1]
-How it might look like I reflected in the draft PR. Feel free to
comment [2]
[1]: https://github.com/apache/polaris/issues/2419
[2]: https://github.com/apache/polaris/pull/2812
