GitLab UX

[mfocko]

Follow-up from the meetings with polkit/bolt maintainers (freedesktop.org GitLab instance) and IRC discussions (gnome.org GitLab instance).

• [x] packit/deployment#401
• [x] packit/packit-service#1914 it is not possible to overwrite the commit status with the same state e.g. running -> running (for test job statuses this means user sees "SRPM build is in progress..." and then "Tests passed..." as a next state) and we also can't do running -> pending
• [ ] packit/deployment#445
• [x] packit/packit-service#1892
• [ ] packit/packit-service#1893

To be refined:

• [ ] extending/refactoring unit tests - should be contained in a separate issue, since they cover more than just GitLab; also the GitLab coverage is minimal, which has been already discovered in dysfunctional Packit on GitLab after a refactor

---

Outcome of the Packit planning for Q1 of '23

• Priority: should
• Benefits that we expect: more users of our service, common and more available automation for the users
• Consumers of those benefits: currently mainly bolt and polkit projects (on freedesktop.org instance), and also all potential users hosting their sources on gitlab.com, freedesktop.org and gnome.org instances

[lachmanfrantisek]

After a team discussion, we didn't pick this as a top Packit team priority for the next quarter and preferred epics with bigger user benefits. (Sadly, we have limited resources.) If anyone wants to help us with this, we will be really glad. We are open to any collaboration and have successfully implemented/started multiple affords thanks to people outside of the Packit team.