Thanks a lot, Kevin! Yufei
On Mon, Nov 17, 2025 at 8:00 AM Kevin Liu <[email protected]> wrote: > Hey folks, > > I have experience setting up infra for pyiceberg. Happy to help here. > > Best, > Kevin Liu > > On Mon, Nov 10, 2025 at 2:49 AM Robert Stupp <[email protected]> wrote: > > > Legally and technically correct LICENSE and NOTICE files cannot be > > automatically generated. > > There is just no way to get the necessary information per published > > artifact to do this, neither for Maven/Java nor for Python packages > > nor for container-images. > > At least not until there is an industry wide accepted and standardized > > way to publish and consume that information. > > > > On Fri, Nov 7, 2025 at 8:44 PM Artur Rakhmatulin > > <[email protected]> wrote: > > > > > > Hi Yufei, thanks for your feedback. > > > > > > I would keep focus on the current topic and make it finalized. > > > I believe LICENSE/NOTICE/DISCLAIMER checks can be automated but it's > not > > > a priority. > > > > > > I synced on this initiative with Honah in DM in Slack and proposed my > > help. > > > > > > Regards, > > > Artur. > > > > > > > > > On 07/11/2025 19:20, Yufei Gu wrote: > > > > Hi Artur, > > > > > > > > Thanks for bringing this up again and for outlining such a clear > plan. > > > > Setting up the PyPI project and nightly Test PyPI builds sounds like > a > > > > great next move. > > > > > > > > One thought: do you think we could automate the LICENSE, NOTICE, and > > > > disclaimer checks as part of the build pipeline? That could make it > > > > reusable for other Python tool publishing efforts, like the MCP > server. > > > > > > > > Yufei > > > > > > > > > > > > On Fri, Nov 7, 2025 at 3:33 AM Artur Rakhmatulin < > > > > [email protected]> wrote: > > > > > > > >> Hi everyone, > > > >> > > > >> I’d like to bring this topic up again so it doesn’t get lost. I’d > like > > > >> to offer my help with this initiative to speed up the package > release > > > >> process. > > > >> > > > >> Thanks a lot for the detailed document — from it, I can already see > > some > > > >> potential steps that need to be completed. > > > >> Since the package name has already been chosen and updated [1], it > > > >> should now be possible to create the project on PyPI.org and > generate > > > >> the necessary publishing keys for the repository. > > > >> From my perspective, here are a few actionable items we could > start > > > >> working on: > > > >> > > > >> * Create the project on PyPI.org and generate the necessary > > publishing > > > >> keys. > > > >> * Begin setting up nightly builds and Test PyPI publication. > > > >> * Complete checks related to LICENSE, NOTICE, and Incubator > > Disclaimer > > > >> (can be done in parallel). > > > >> * Create corresponding GitHub issues under the Python Package > > > >> Maintenance [2] project and assign volunteers to increase > > visibility > > > >> and track progress. > > > >> > > > >> What do you think about this plan? > > > >> > > > >> Regards, > > > >> Artur > > > >> > > > >> [1]: https://github.com/apache/polaris/issues/2699 > > > >> > > > >> [2]: https://github.com/orgs/apache/projects/540/views/1 > > > >> > > > >> > > > >> On 15/10/2025 07:58, Jean-Baptiste Onofré wrote: > > > >>> Hi > > > >>> > > > >>> I'm supporting this. However, as packages on PyPi are considered as > > > >>> "release artifacts", it has to be legally correct regarding The ASF > > > >>> policy. > > > >>> > > > >>> Several Apache projects already publish PyPi packages (for instance > > > >>> https://superset.apache.org/docs/installation/pypi/). > > > >>> As we are in the incubator, we have to keep the incubating "tag". > > > >>> > > > >>> I will do a pass and check with you. > > > >>> > > > >>> Regards > > > >>> JB > > > >>> > > > >>> On Tue, Oct 14, 2025 at 6:17 PM Honah J.<[email protected]> wrote: > > > >>>> Hi everyone, > > > >>>> > > > >>>> I’d like to start a discussion about publishing the Apache Polaris > > > >> Python > > > >>>> CLI to PyPI and providing nightly builds (test PyPi). > > > >>>> > > > >>>> The main goal is to make the CLI easier to install (pip install > > > >>>> <package_name>) and to align its release and distribution process > > with > > > >> ASF > > > >>>> guidelines. I’ve drafted a proposal [1] that outlines the key > > > >> requirements > > > >>>> and the high-level release process if we include the Python CLI in > > the > > > >> next > > > >>>> release. The proposal also covers how we might set up nightly > > builds on > > > >>>> Test PyPI for early testing. > > > >>>> > > > >>>> While some details can be finalized later, I’d like to first > gather > > > >>>> feedback on the overall direction — specifically, whether the > > community > > > >>>> agrees with publishing to PyPI and providing nightly builds. > > > >>>> > > > >>>> If there’s general agreement, I plan to open two separate [VOTE] > > > >> threads to > > > >>>> formalize these decisions: > > > >>>> 1. Whether to the Python CLI to PyPI > > > >>>> 2. Whether to provide nightly build (publish to test PyPi) > > > >>>> > > > >>>> Please let me know what you think! > > > >>>> > > > >>>> [1] > > > >>>> > > > >> > > > https://docs.google.com/document/d/1gbKYnFftpq884GhJ59waHdfoQG6MrevVAVCspf3hbrk/edit?usp=sharing > > > >>>> > > > >>>> Best regards, > > > >>>> Jonas > > >
