Hello. Thanks all for the provided details regarding the processes and rituals in the Apache OOS community. For me it sounds reasonable to start a separate VOTE thread where I will provide additional details, as I did in the PR description with the explanations and examples. I will prepare a message and start a new dev-mailinglist VOTing thread tomorrow.
вт, 14 окт. 2025 г. в 23:18, Dmitri Bourlatchkov <[email protected]>: > Hi All, > > I suppose the vote that Jonas proposed on the package name will need to > follow the consensus approval approach (since it ultimately affects code) > without a lazy consensus [1] (using lazy consensus for this would be the > same as approving the corresponding PR). If that passes, we'll still follow > the normal PR process (with lazy consensus) for implementing the change. > > Running a formal vote sounds useful indeed, as the name will be exposed in > external systems for a long time. > > Separate voting on the package name and tool name sounds good to me. > > [1] https://www.apache.org/foundation/voting > > Cheers, > Dmitri. > > On Tue, Oct 14, 2025 at 4:48 PM Honah J. <[email protected]> wrote: > > > Hi Artur, > > > > Thanks for the clarification and for putting together the draft PR! > > > > I was mainly thinking that it might help to have a separate [VOTE] thread > > to keep the decision record clear, especially since the package rename is > > quite a significant change. Once the package is released and published to > > PyPI, it’s something we can hardly change later. Since this thread > doesn’t > > have “[VOTE]” in the title or mention it explicitly, it might be a bit > > harder for others later to trace where the final decision was made. > > > > It’s also common to follow up a discussion with a quick vote thread — the > > discussion captures everyone’s thoughts, and the vote just helps > formalize > > the outcome. And since we actually have two related topics — the package > > rename and the tool rename — separating them could make things even > easier > > to track. > > > > WDYT? > > > > Best regards, > > Jonas > > > > > > > > On Tue, Oct 14, 2025 at 3:09 PM artur rakhmatulin < > > [email protected]> wrote: > > > > > Hello everyone. Thank you for your comment. > > > > > > Sure, it looks like we all agreed with the "apache-polaris" as python > > > package name. > > > Today I was working on the preparation of the necessary changes and > want > > to > > > share with you a draft PR. > > > Please check it out: [1] > > > In the PR description, I was explained the proposed changes, so feel > free > > > to share your thoughts. > > > > > > Also, I'm not sure if I need to start an addition VOTE thread in > > > dev-mailing lists. The Idea of this thread was to vote here. > > > But if it is necessary, I can start a new thread. > > > > > > [1]: https://github.com/apache/polaris/pull/2812 > > > > > > вт, 14 окт. 2025 г. в 17:44, Yufei Gu <[email protected]>: > > > > > > > +1 on "apache-polaris" as the Pypi project name. I am OK with either > > > > "pypolaris" or "polaris" as the tool name. The chance of conflicts > > would > > > > be minimal. > > > > > > > > Yufei > > > > > > > > > > > > On Tue, Oct 14, 2025 at 9:36 AM Honah J. <[email protected]> wrote: > > > > > > > > > It looks like we’ve reached a general agreement that > “apache-polaris” > > > > would > > > > > be a good package name for the Python CLI. For the tool name, we > seem > > > > > comfortable keeping “polaris”, while we can keep that discussion > open > > > in > > > > > case others want to chime in > > > > > > > > > > @Artur --- Shall we start a vote on adopting *“apache-polaris”* as > > the > > > > > package name? > > > > > > > > > > Best regards, > > > > > Jonas > > > > > > > > > > On Wed, Oct 8, 2025 at 3:28 PM Travis Bowen < > [email protected]> > > > > > wrote: > > > > > > > > > > > Thanks for starting this Artur. > > > > > > Thankful that 'apache-polaris' is available for the distribution! > > > > > > For the tool name - I have a slight preference for just 'polaris' > > but > > > > > don't > > > > > > have strong opinions one way or the other. > > > > > > > > > > > > -Travis > > > > > > > > > > > > On Wed, Oct 8, 2025 at 1:10 PM Michael Collado < > > > [email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > > +1 on apache-polaris. Very easy to remember and > straightforward. > > I > > > > > > > personally dislike the "py" prefix on everything - like the > J... > > > > > > convention > > > > > > > on things in Java that was common for a while. I know what > > language > > > > I'm > > > > > > > using. You don't need to remind me 😂. But I understand it's a > > > common > > > > > > > convention, so it doesn't bother me too much. > > > > > > > > > > > > > > Mike > > > > > > > > > > > > > > On Wed, Oct 8, 2025 at 10:53 AM artur rakhmatulin < > > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > Hello everyone, > > > > > > > > Thank you all for attending this discussion. > > > > > > > > > > > > > > > > The “apache-polaris” distribution name is available, so we > can > > > use > > > > > it. > > > > > > I > > > > > > > > also like how it’s structured in the Apache Flink project — a > > > great > > > > > > > > example, thank you for sharing it. > > > > > > > > > > > > > > > > Regarding the shorter name for the tool, I agree that we can > > keep > > > > it > > > > > > the > > > > > > > > same, but I’m a bit concerned about potential naming > collisions > > > > with > > > > > > > > existing tools. In any case, both “polaris” and “pypolaris” > are > > > > > > > acceptable > > > > > > > > options. Personally, I prefer “pypolaris”, as it follows the > > same > > > > > > naming > > > > > > > > convention used in the Apache Flink project. > > > > > > > > > > > > > > > > @Honah — The project name and the executable tool name can > > > differ; > > > > > it’s > > > > > > > not > > > > > > > > mandatory for them to match the distribution name. > > > > > > > > So, I don’t think this should be a problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ср, 8 окт. 2025 г. в 17:47, Honah J. <[email protected]>: > > > > > > > > > > > > > > > > > Unfortunately, `pypolaris` is also taken by another > project: > > > > > > > > > https://pypi.org/project/pypolaris/#description > > > > > > > > > > > > > > > > > > On Tue, Oct 7, 2025 at 2:15 PM Yufei Gu < > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Thanks for bringing this up! "apache-polaris" as a Pypi > > repo > > > > name > > > > > > > > sounds > > > > > > > > > > good to me. Flink uses the same naming schema: > > > > > > > > > > https://pypi.org/project/apache-flink/. > > > > > > > > > > > > > > > > > > > > Are we still able to use a shorter package name like > > > > "pypolaris"? > > > > > > For > > > > > > > > > > example, Flink's package name is pyflink[1]. > > > > > > > > > > > > > > > > > > > > from pyflink.common import Row > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/python/table_api_tutorial/ > > > > > > > > > > > > > > > > > > > > Yufei > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Oct 7, 2025 at 10:34 AM Dmitri Bourlatchkov < > > > > > > > [email protected]> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi Anna and All, > > > > > > > > > > > > > > > > > > > > > > > - polaris-catalog - taken > > > > > > > > https://pypi.org/project/polaris-catalog/ > > > > > > > > > > > > > > > > > > > > > > Apparently it is taken by Anna [1] who is a Polaris > > > > committer. > > > > > > > > > > > > > > > > > > > > > > Does anyone know previous plans for that project? > > > > > > > > > > > > > > > > > > > > > > [1] https://home.apache.org/phonebook.html?uid=annafil > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > Dmitri. > > > > > > > > > > > > > > > > > > > > > > On Tue, Oct 7, 2025 at 6:29 AM artur rakhmatulin < > > > > > > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello everyone! > > > > > > > > > > > > As part of the "Package Python CLI tool in the binary > > > > > > > distribution > > > > > > > > > > #2419" > > > > > > > > > > > > initiative [1], we need to agree on the package name > > for > > > > > Apache > > > > > > > > > Polaris > > > > > > > > > > > > Catalog that will be used for publishing to PyPI. > > > > > > > > > > > > The current name "polaris" cannot be used as it's > > already > > > > > taken > > > > > > > by > > > > > > > > > > > another > > > > > > > > > > > > package unrelated to Apache Polaris. > > > > > > > > > > > > I've created a separate Github Issue [2] to discuss > > this > > > > > > matter. > > > > > > > > > > > > > > > > > > > > > > > > Proposed options: > > > > > > > > > > > > - apache-polaris - available > > > > > > > > > > > > - polaris-catalog - taken > > > > > > > > https://pypi.org/project/polaris-catalog/ > > > > > > > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > TLDR; > > > > > > > > > > > > ??? Is this a CLI or SDK? > > > > > > > > > > > > The current implementation is not just a CLI tool, > but > > > > also a > > > > > > > > > library. > > > > > > > > > > > > After the package is delivered to PyPI, users will be > > > able > > > > to > > > > > > use > > > > > > > > the > > > > > > > > > > CLI > > > > > > > > > > > > tool as well as import the library into their > projects. > > > > > > > > > > > > The CLI tool name is defined through the > > > [project.scripts] > > > > > > > > > > configuration > > > > > > > > > > > in > > > > > > > > > > > > the pyproject.toml file [3] > > > > > > > > > > > > > > > > > > > > > > > > Example: > > > > > > > > > > > > ``` > > > > > > > > > > > > [project.scripts] > > > > > > > > > > > > polaris-catalog-cli = "cli.polaris_cli:main" > > > > > > > > > > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > When installing the package via "pipx install > > > > > apache-polaris", > > > > > > > the > > > > > > > > > bin > > > > > > > > > > > file > > > > > > > > > > > > will be available in ~/.local/bin/ > > > > > > > > > > > > > polaris-catalog-cli --help > > > > > > > > > > > > > > > > > > > > > > > > This means that to use the CLI, there's no need to > > clone > > > > the > > > > > > > entire > > > > > > > > > > > > project. > > > > > > > > > > > > > > > > > > > > > > > > ??? How does it work now? > > > > > > > > > > > > Currently, to use the CLI you need to clone the > entire > > > > > project > > > > > > > and > > > > > > > > > use > > > > > > > > > > > > ./polaris from the project root directory. When > calling > > > > > > > ./polaris, > > > > > > > > > > > > automatic initialization of the Python environment > > > occurs. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > +-------------------------------------------------------------+ > > > > > > > > > > > > | cd polaris && ./polaris | > > > > > > > > > > > > > > > > > +-------------------------------------------------------------+ > > > > > > > > > > > > > > > > > +-------------------------------------------------------------+ > > > > > > > > > > > > | python environment inside ./polaris project dir | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > | | 1 - check ./polaris-venv | | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > | v | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | | 1.1 - initialize ./polaris-venv through | | > > > > > > > > > > > > | | python3 -m venv | | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > | | 2 - activate python env > ./polaris-venv/bin/activate > > > | | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > | v | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | | 2.1 - install dependencies | | > > > > > > > > > > > > | | ./regtests/requirements.txt | | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | v | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | | 2.2 - ./poetry install ./client/python | | > > > > > > > > > > > > | +------------------------------------------+ | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > | | 3 - calling ./polaris -> > ./polaris-venv/bin/polaris > > > | | > > > > > > > > > > > > | > > > > +-------------------------------------------------------+ | > > > > > > > > > > > > > > > > > +-------------------------------------------------------------+ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1]: https://github.com/apache/polaris/issues/2419 > > > > > > > > > > > > [2]: https://github.com/apache/polaris/issues/2699 > > > > > > > > > > > > [3]: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/polaris/blob/main/client/python/pyproject.toml#L45 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Best regards, Artur Rakhmatulin > > > > > > > > > > > > e-mail: [email protected], > > > > > > > > > > > > telegram: https://t.me/binarycat0 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Best regards, Artur Rakhmatulin > > > > > > > > e-mail: [email protected], > > > > > > > > telegram: https://t.me/binarycat0 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Best regards, Artur Rakhmatulin > > > e-mail: [email protected], > > > telegram: https://t.me/binarycat0 > > > > > > -- Best regards, Artur Rakhmatulin e-mail: [email protected], telegram: https://t.me/binarycat0
