User interviews to align Packit dashboard with people's need

[Venefilyn]

Description

To see what is next for the Packit Dashboard we should interview teams that use Packit and other users. We currently have a good grasp on the service part of Packit but lack the consolidation aspect of it -- that is, a more advanced but easier to use Packit dashboard. Which is why I've coined Project Mycorrhiza to align Packit dashboard with these potential improvements.

With this in mind we should look into existing research around apps and teams to see what would apply for Packit as well, together with our own questions to get an idea for the future of Packit dashboard.

I've been working with @lachmanfrantisek who has created a feedback form for us to ask internal Red Hat users of Packit as it is the most visible way for us to gather feedback, but we would love to have feedback from public users as well. Once we are ready to begin to ask teams we should also publish this ask in discussion section of Packit and advertise it.

I have also reached out to and had a meeting with a manager from the Red Hat UXD (User Experience Design) Team to see if they can help us improve the feedback form before we start asking teams and help us analyze the results in a methodical way.

The results of the user interviews are likely to indicate improvements to Packit and Packit Service as a whole as well.

Benefit

Current scope of Packit dashboard aligns features of Packit service to a visual component in the dashboard. There is little push for changes around the dashboard or visualizing results in a researched way. As Packit dashboard has huge potential to be a great improvement to the developer workflow we should scope out what the most impactful changes would be to ensure fewer hurdles for developers.

Packit is a tool to help developers "pack it". It is meant to reduce the developer barrier by a huge margin and it serves that purpose greatly in the state it is in currently. However, it misses the beat once an application has enrolled in Packit by providing the data developers needs in as few hurdles as possible. In the issue #436 this is evident as it included a lot of steps and high mental complexity to get the results developer needs

Importance

Hugely important to the Packit dashboard to ensure its goals align with the greatest needs of both Packits users and Fedora packagers. Not only does this help Packit dashboard but also Packit service to help align for changes that users benefit to the most.

Workaround

• There is an existing workaround that can be used until this feature is implemented.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)