Clarification on relationship between pulp-ui-2 and legacy pulp-ui

[rojo1997]

Hi there 👋,

Thank you for the work on pulp-ui-2 — it looks very promising!

I have a question regarding the relationship between this repository (pulp-ui-2) and the legacy UI (pulp/pulp-ui):

1. Is pulp-ui-2 intended to replace pulp-ui entirely?
2. If so, what is the timeline or plan for deprecating the legacy pulp-ui?
3. Will there be any migration guidance for existing users moving from pulp-ui to pulp-ui-2?

It would be great to understand the roadmap and direction for these UI projects so we can plan accordingly in our usage.

Thanks in advance! 😊

[carlosthe19916]

Hi @rojo1997 , thanks for reaching out!

1. Is pulp-ui-2 intended to replace pulp-ui entirely?

At this moment, this repository covers a different use case compared to the https://github.com/pulp/pulp-ui repository.

The initial and main objective of https://github.com/pulp/pulp-ui-2 as of today is to bring a way to expose Pulp Packages to the public (unauthenticated users) just like any major package provider would do. E.g. https://crates.io/ , https://pypi.org/ or https://www.npmjs.com/

My personal view of the 2 repositories are:

• https://github.com/pulp/pulp-ui focuses more on Admin tasks
• https://github.com/pulp/pulp-ui-2 focuses on public available data, again this aims to be similar to the public search engine part of https://crates.io/ , https://pypi.org/ or https://www.npmjs.com/

Having said that, we are still in an early stage and need time to evaluate how the 2 repositories can either complement each other or merge in the future; but we'll need time to take a decision. I hope that makes sense.

Do you use https://github.com/pulp/pulp-ui? It would be interesting to know how the current https://github.com/pulp/pulp-ui is used and what are the expectations of the community