rename MetaCPAN::API

[haarg]

MetaCPAN::API is a poor choice for a package name, since there is already a module with that name on CPAN. This is confusing and could lead to weird issues if we ever pulled in a dependency that was still using MetaCPAN::API.

[jberger]

It was chosen to be symmetric with ::Web. I see those modules are yours and are deprecated. Is there any chance we could just remove them? Otherwise, what name do you propose?

[haarg]

I took over maintenance of MetaCPAN::API to do fixes allow it to continue working with the v1 API. It has enough code dependent on it that I have no intention of removing it.

Some names without much thought put into them: MetaCPAN::APIServer MetaCPAN::Server::API (and maybe even moving web to MetaCPAN::Server::Web) metacpan::api

[oalders]

I like MetaCPAN::Server::API or even MetaCPAN::Service::API.

[mickeyn]

MetaCPAN::App::API || MetaCPAN::WebApp::API?

Because the MetaCPAN::Server namespace is used by the Catalyst setup and will take some time before a full transition, I'd rather have some separation to avoid confusion of what belongs to which framework.

[ssoriche]

I like MetaCPAN::APIServer as it's pretty explicit as to what it is, without colliding with the existing Catalyst implementation.

[mohawk2]

Was this discussed / resolved at PTS 2019?

[oalders]

No, I don't think there's any resolution on this. MetaCPAN::APIServer seems like the most succinct of the suggestions.

[mohawk2]

You're quite right it's succinct. It does read a bit wrong to me, just because I'd prefer to not combine two "words" (API and server) without a :: between. However, it's not my call :-)

[szabgab]

Maybe MetaCPAN::Public::API