Identify the data required to redesign the Package UI
Problem to solve
The Package stage allows you to publish, consume and discover packages, all in one place. We currently support Docker images/tags as well NPM and Maven packages. Users publish and pull packages using GitLab CI/CD, the command line or the GitLab API.
The problem is that we currently do not expose most of the useful metadata to users to about how an image or package was built, by whom or when and where it was last used. In order to provide a more robust, intuitive experience, we will identify what data is needed to help the user understand and navigate through the product. This data model will inform product priorities as well as help prototyping and testing a new, improved user experience for the Package stage.
Based on user research:
- Identify the various data required to help users better understand the package and container registry
- Document where the data comes from and whether or not it is available or feasible
Identifying the data model, will create a clearer picture of how to redesign the UI and allow us to build prototypes that we can test and validate with users.
What does success look like, and how can we measure that?
Success looks like we have documented, based on user research, the various data and fields that are required to help a user better understand how a group or projects images/packages have been built, by whom and where/when it was last used.