Interviews: Understanding package data user needs and wants
Discussion Guide: Doc
What’s this issue all about?
Understand why certain pieces of package/registry data are important to users.
Better understand how package data is being used.
Who is the target user of the feature?
Users who interact directly with the container registry or package registry.
- Systems administrators
- Software developers
- Dev-ops engineers
What questions are you trying to answer?
When do users come to package to look up pieces of data? What are they hoping to accomplish with different data points?
Core questions
What data is most important to the users and why? What are the users hoping to accomplish by gathering this data?
Additional questions
If there are opportunities for connecting package with other parts of the GitLab environment (like Ci/CD or Creation)
What hypotheses and/or assumptions do you have?
- Users are coming to Package to confirm the Ci/CD pipeline worked as expected
- Users want to know what file/branch/MR/pipeline created an asset for bug fixing/optimisation
- Users have a few special packages/images, but have many artefacts being created they don't care about
What decisions will you make based on the research findings?
- The package/container registry UI/IA
- Informed feature priorities
What's the latest milestone that the research will still be useful to you?
%12.5+ This will help inform foundational elements of the package offering.
Edited by Rayana Verissimo