Artifact rename proposals for server and tooling

projectnessie / nessie

Nessie: Transactional Catalog for Data Lakes with Git-like semantics

https://projectnessie.org

Apache License 2.0

974 stars 124 forks source link

Artifact rename proposals for server and tooling #8245

Closed snazy closed 4 months ago

snazy commented 5 months ago

Rename proposals:

Artifact :nessie-quarkus to :nessie-server (container image name stays as it is)
- also update the quarkus-app-name to nessie-server (currently: quarkus-app)
Artifact :nessie-quarkus-cli to :nessie-server-admin
- also update the quarkus-app-name to nessie-server-admin (currently: quarkus-app)
Artifact :nessie-quarkus-tests to :nessie-server-tests
Artifact :nessie-quarkus-common to :nessie-server-common
Artifact :nessie-quarkus-auth to :nessie-server-auth

(Ignoring CLI tools in this issue)

/cc @adutra @dimas-b

snazy commented 4 months ago

Thinking a bit more about this proposal, it's probably not good to implement this, because a) a lot of documentation changes are needed b) basically all downstream components (helm chart, k8s operator) would break c) breaking changes for users

adutra commented 4 months ago

Sorry, but I disagree for :nessie-quarkus-cli: it's a bad name. I think we should tackle that part of the proposal.

dimas-b commented 4 months ago

nessie-quarkus-cli is a standalone tool. Renaming it should not have any downstream effects.

dimas-b commented 4 months ago

Not sure if we have a separate issue for that, but renaming the "content generator" tool might also be worth the trouble for the sake of clarify for end users.

snazy commented 4 months ago

I'm okay w/ renaming these two tools. Can you open issues or PRs?

adutra commented 4 months ago

For nessie-quarkus-cli: https://github.com/projectnessie/nessie/issues/8481 – will tackle it soon-ish