Hi Yufei,

This name looks good! Exciting progress thus far!

Go community,

Adam

On Tue, Nov 18, 2025 at 6:14 PM Jean-Baptiste Onofré <[email protected]>
wrote:

> Hi Yufei,
>
> The name looks good to me (it's descriptive and accurate, following
> the naming convention).
>
> Thanks !
>
> Regards
> JB
>
> On Tue, Nov 18, 2025 at 10:34 AM Yufei Gu <[email protected]> wrote:
> >
> > Hi folks,
> >
> > I’d like to propose standardizing the PyPI package name for the new
> Polaris
> > MCP server as *apache-polaris-mcp.*
> >
> > This follows the naming conventions used by other Apache projects on PyPI
> > (e.g., apache-airflow, apache-beam, apache-libcloud) and matches PyPI’s
> > canonical normalization rules. Using the lowercase hyphenated form
> directly
> > keeps things consistent for users, avoids normalization surprises, and
> > aligns better with ASF branding.
> >
> > This also follows the naming convention we discussed
> > <https://lists.apache.org/thread/7fnnwdb2rnxmb2tk0yo8jh5mt7s325dx> for
> > Polaris CLI tool. A clarification regarding packaging:
> > The MCP server package cannot be combined with the Polaris CLI tools
> > package, even if we wanted to. The two components live in different
> > repositories and use separate pyproject.toml configurations. Because of
> > this, there is no clean or practical way to publish them as a single PyPI
> > distribution without major restructuring(e.g., moving MCP server to the
> > main repo).
> >
> > If there are concerns or alternative suggestions, please reply.
> >
> > Thanks,
> > Yufei
>

Reply via email to