Thanks for the proposal! There seems to be some confusion here, I think Artur is proposing to add a project/board for the python package instead of migrating the client to a separate repo? I share the same idea that python CLI would be better to remain in the polaris main repo since it is widely used in regtests and Quickstart examples.
Project/Board sounds good to me! I think we could also add a label for all python cli related issues and PRs, so people could easily filter by that. Best regards, Jonas On Thu, Oct 16, 2025 at 12:20 PM Dmitri Bourlatchkov <[email protected]> wrote: > Hi Artur, > > Having a dedicated repository for the Python CLI sounds reasonable to me in > general. > > One thing we probably need to clarify is how it will track the evolution of > Polaris APIs. Currently the CLI builds and uses the exact same API spec as > the Polaris server code (from the same repo). How do you envision managing > that in a separate repo? > > Thanks, > Dmitri. > > On Thu, Oct 16, 2025 at 12:53 PM Artur Rakhmatulin < > [email protected]> wrote: > > > Hello everyone! > > > > I have a proposal to create a Project/Board in Github for "Python > > Package Maintenance", here: [1] > > > > > > Motivation: > > > > - Easily track the progress of all initiatives, e.g Python package > > distribution. > > > > - Gather and create/assign all issues related to Apache Polaris Python > > client implementation to be focused on this scope who is interested. > > > > > > Ex: > > > > - [2] > > > > - [3] > > > > - [4] > > > > - [5] > > > > - [6] > > > > ... etc > > > > > > [1]: https://github.com/apache/polaris/projects?query=is%3Aopen > > > > [2]: https://github.com/apache/polaris/issues/2699 > > > > [3]: https://github.com/apache/polaris/issues/2419 > > > > [4]: https://github.com/apache/polaris/pull/931 > > > > [5]: https://github.com/apache/polaris/issues/2709 > > > > [6]: https://github.com/apache/polaris/issues/2769 > > > > > > > > >
