You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Artur Rakhmatulin <ar...@gmail.com> on 2025/10/26 10:43:38 UTC
[VOTE] pypolaris as Apache Polaris CLI tool
Hello everyone.
I would like to reopen 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.
Previous VOTE thread:
https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
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:
https://github.com/apache/polaris/issues/2419
- How it might look like I reflected in the draft PR. Feel free to
comment: https://github.com/apache/polaris/pull/2812
Please vote in the next 72 hours.
[ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
[ ] +0
[ ] -1 Do not change name to "pypolaris" because ...
Only PPMC members and mentors have binding votes, but other community
members are encouraged to cast non-binding votes. This vote will pass if
there are
3 binding +1 votes and more binding +1 votes than -1 votes.
Best,
Artur Rakhmatulin
Re: [VOTE] pypolaris as Apache Polaris CLI tool
Posted by Artur Rakhmatulin <ar...@gmail.com>.
Hello Yufei, thanks for bumping this up.
I would consider this VOTE as CLOSED since enough time has passed and it
did not receive the community feedback. We can revisit this issue later
if needed.
Regards,
Artur.
On 05/11/2025 18:29, Yufei Gu wrote:
> -1 based on the reasons I mentioned in my previous email.
>
> Can we wrap this up soon? The module name change feels quite trivial, TBH.
> The key consideration should be the potential for conflicts with other
> projects when the Polaris Python library is used downstream. The likelihood
> of such conflicts is effectively the same whether we use “pyPolaris” or
> “polaris.”
>
> Also, we should move forward with publishing the Python binary instead of
> spending more time debating the name.
> Yufei
>
>
> On Mon, Oct 27, 2025 at 12:02 PM Yufei Gu <fl...@gmail.com> wrote:
>
>> Hi Artur,
>>
>> Thanks a lot for raising this. I'd prefer to keep "polaris" as the module
>> name of the Polaris python code. "pyPolaris" sounds unnecessary to me.
>> However, I'm not fully understand the conflict between the module name
>> "polaris" and the ./polaris executable. Would you mind clarifying it a bit?
>>
>> BTW, https://github.com/apache/polaris/pull/2812 may not be a good
>> example, as it uses "apache_polaris" as the module name, rather than
>> "pyPolaris"
>>
>> Yufei
>>
>>
>> On Sun, Oct 26, 2025 at 3:43 AM Artur Rakhmatulin <
>> artur.rakhmatulin@gmail.com> wrote:
>>
>>> Hello everyone.
>>> I would like to reopen 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.
>>>
>>> Previous VOTE thread:
>>> https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
>>>
>>> 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:
>>> https://github.com/apache/polaris/issues/2419
>>> - How it might look like I reflected in the draft PR. Feel free to
>>> comment: https://github.com/apache/polaris/pull/2812
>>>
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
>>> [ ] +0
>>> [ ] -1 Do not change name to "pypolaris" because ...
>>>
>>> Only PPMC members and mentors have binding votes, but other community
>>> members are encouraged to cast non-binding votes. This vote will pass if
>>> there are
>>> 3 binding +1 votes and more binding +1 votes than -1 votes.
>>>
>>> Best,
>>> Artur Rakhmatulin
>>>
>>>
Re: [VOTE] pypolaris as Apache Polaris CLI tool
Posted by Yufei Gu <fl...@gmail.com>.
Thanks a lot for closing this, Artur! Let's move forward with python binary
publishing.
Yufei
On Wed, Nov 5, 2025 at 11:28 AM Artur Rakhmatulin <
artur.rakhmatulin@gmail.com> wrote:
> Just to clarify, the reason I closed the vote:
> Given that this is a vote on code modification [1], I am assuming that
> Yufei's -1 is considered a veto [2] with the technical justification
> that ""pyPolaris" sounds unnecessary".
>
> I'll consider this vote closed and move onto publishing the binary.
>
> [1] -
> https://www.apache.org/foundation/voting.html#votes-on-code-modification
> [2] - https://www.apache.org/foundation/voting.html#Veto
>
>
> On 05/11/2025 18:29, Yufei Gu wrote:
> > -1 based on the reasons I mentioned in my previous email.
> >
> > Can we wrap this up soon? The module name change feels quite trivial,
> TBH.
> > The key consideration should be the potential for conflicts with other
> > projects when the Polaris Python library is used downstream. The
> likelihood
> > of such conflicts is effectively the same whether we use “pyPolaris” or
> > “polaris.”
> >
> > Also, we should move forward with publishing the Python binary instead of
> > spending more time debating the name.
> > Yufei
> >
> >
> > On Mon, Oct 27, 2025 at 12:02 PM Yufei Gu <fl...@gmail.com> wrote:
> >
> >> Hi Artur,
> >>
> >> Thanks a lot for raising this. I'd prefer to keep "polaris" as the
> module
> >> name of the Polaris python code. "pyPolaris" sounds unnecessary to me.
> >> However, I'm not fully understand the conflict between the module name
> >> "polaris" and the ./polaris executable. Would you mind clarifying it a
> bit?
> >>
> >> BTW, https://github.com/apache/polaris/pull/2812 may not be a good
> >> example, as it uses "apache_polaris" as the module name, rather than
> >> "pyPolaris"
> >>
> >> Yufei
> >>
> >>
> >> On Sun, Oct 26, 2025 at 3:43 AM Artur Rakhmatulin <
> >> artur.rakhmatulin@gmail.com> wrote:
> >>
> >>> Hello everyone.
> >>> I would like to reopen 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.
> >>>
> >>> Previous VOTE thread:
> >>> https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
> >>>
> >>> 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:
> >>> https://github.com/apache/polaris/issues/2419
> >>> - How it might look like I reflected in the draft PR. Feel free to
> >>> comment: https://github.com/apache/polaris/pull/2812
> >>>
> >>>
> >>> Please vote in the next 72 hours.
> >>>
> >>> [ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
> >>> [ ] +0
> >>> [ ] -1 Do not change name to "pypolaris" because ...
> >>>
> >>> Only PPMC members and mentors have binding votes, but other community
> >>> members are encouraged to cast non-binding votes. This vote will pass
> if
> >>> there are
> >>> 3 binding +1 votes and more binding +1 votes than -1 votes.
> >>>
> >>> Best,
> >>> Artur Rakhmatulin
> >>>
> >>>
>
Re: [VOTE] pypolaris as Apache Polaris CLI tool
Posted by Artur Rakhmatulin <ar...@gmail.com>.
Just to clarify, the reason I closed the vote:
Given that this is a vote on code modification [1], I am assuming that
Yufei's -1 is considered a veto [2] with the technical justification
that ""pyPolaris" sounds unnecessary".
I'll consider this vote closed and move onto publishing the binary.
[1] -
https://www.apache.org/foundation/voting.html#votes-on-code-modification
[2] - https://www.apache.org/foundation/voting.html#Veto
On 05/11/2025 18:29, Yufei Gu wrote:
> -1 based on the reasons I mentioned in my previous email.
>
> Can we wrap this up soon? The module name change feels quite trivial, TBH.
> The key consideration should be the potential for conflicts with other
> projects when the Polaris Python library is used downstream. The likelihood
> of such conflicts is effectively the same whether we use “pyPolaris” or
> “polaris.”
>
> Also, we should move forward with publishing the Python binary instead of
> spending more time debating the name.
> Yufei
>
>
> On Mon, Oct 27, 2025 at 12:02 PM Yufei Gu <fl...@gmail.com> wrote:
>
>> Hi Artur,
>>
>> Thanks a lot for raising this. I'd prefer to keep "polaris" as the module
>> name of the Polaris python code. "pyPolaris" sounds unnecessary to me.
>> However, I'm not fully understand the conflict between the module name
>> "polaris" and the ./polaris executable. Would you mind clarifying it a bit?
>>
>> BTW, https://github.com/apache/polaris/pull/2812 may not be a good
>> example, as it uses "apache_polaris" as the module name, rather than
>> "pyPolaris"
>>
>> Yufei
>>
>>
>> On Sun, Oct 26, 2025 at 3:43 AM Artur Rakhmatulin <
>> artur.rakhmatulin@gmail.com> wrote:
>>
>>> Hello everyone.
>>> I would like to reopen 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.
>>>
>>> Previous VOTE thread:
>>> https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
>>>
>>> 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:
>>> https://github.com/apache/polaris/issues/2419
>>> - How it might look like I reflected in the draft PR. Feel free to
>>> comment: https://github.com/apache/polaris/pull/2812
>>>
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
>>> [ ] +0
>>> [ ] -1 Do not change name to "pypolaris" because ...
>>>
>>> Only PPMC members and mentors have binding votes, but other community
>>> members are encouraged to cast non-binding votes. This vote will pass if
>>> there are
>>> 3 binding +1 votes and more binding +1 votes than -1 votes.
>>>
>>> Best,
>>> Artur Rakhmatulin
>>>
>>>
Re: [VOTE] pypolaris as Apache Polaris CLI tool
Posted by Yufei Gu <fl...@gmail.com>.
-1 based on the reasons I mentioned in my previous email.
Can we wrap this up soon? The module name change feels quite trivial, TBH.
The key consideration should be the potential for conflicts with other
projects when the Polaris Python library is used downstream. The likelihood
of such conflicts is effectively the same whether we use “pyPolaris” or
“polaris.”
Also, we should move forward with publishing the Python binary instead of
spending more time debating the name.
Yufei
On Mon, Oct 27, 2025 at 12:02 PM Yufei Gu <fl...@gmail.com> wrote:
> Hi Artur,
>
> Thanks a lot for raising this. I'd prefer to keep "polaris" as the module
> name of the Polaris python code. "pyPolaris" sounds unnecessary to me.
> However, I'm not fully understand the conflict between the module name
> "polaris" and the ./polaris executable. Would you mind clarifying it a bit?
>
> BTW, https://github.com/apache/polaris/pull/2812 may not be a good
> example, as it uses "apache_polaris" as the module name, rather than
> "pyPolaris"
>
> Yufei
>
>
> On Sun, Oct 26, 2025 at 3:43 AM Artur Rakhmatulin <
> artur.rakhmatulin@gmail.com> wrote:
>
>> Hello everyone.
>> I would like to reopen 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.
>>
>> Previous VOTE thread:
>> https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
>>
>> 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:
>> https://github.com/apache/polaris/issues/2419
>> - How it might look like I reflected in the draft PR. Feel free to
>> comment: https://github.com/apache/polaris/pull/2812
>>
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
>> [ ] +0
>> [ ] -1 Do not change name to "pypolaris" because ...
>>
>> Only PPMC members and mentors have binding votes, but other community
>> members are encouraged to cast non-binding votes. This vote will pass if
>> there are
>> 3 binding +1 votes and more binding +1 votes than -1 votes.
>>
>> Best,
>> Artur Rakhmatulin
>>
>>
Re: [VOTE] pypolaris as Apache Polaris CLI tool
Posted by Yufei Gu <fl...@gmail.com>.
Hi Artur,
Thanks a lot for raising this. I'd prefer to keep "polaris" as the module
name of the Polaris python code. "pyPolaris" sounds unnecessary to me.
However, I'm not fully understand the conflict between the module name
"polaris" and the ./polaris executable. Would you mind clarifying it a bit?
BTW, https://github.com/apache/polaris/pull/2812 may not be a good example,
as it uses "apache_polaris" as the module name, rather than "pyPolaris"
Yufei
On Sun, Oct 26, 2025 at 3:43 AM Artur Rakhmatulin <
artur.rakhmatulin@gmail.com> wrote:
> Hello everyone.
> I would like to reopen 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.
>
> Previous VOTE thread:
> https://lists.apache.org/thread/6l1696679f7zq922f3kowd4fr3vcfr28
>
> 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:
> https://github.com/apache/polaris/issues/2419
> - How it might look like I reflected in the draft PR. Feel free to
> comment: https://github.com/apache/polaris/pull/2812
>
>
> Please vote in the next 72 hours.
>
> [ ] +1 Change Apache Polaris CLI tool name to "pypolaris"
> [ ] +0
> [ ] -1 Do not change name to "pypolaris" because ...
>
> Only PPMC members and mentors have binding votes, but other community
> members are encouraged to cast non-binding votes. This vote will pass if
> there are
> 3 binding +1 votes and more binding +1 votes than -1 votes.
>
> Best,
> Artur Rakhmatulin
>
>