Michael Catanzaro <mcatanzaro@xxxxxxxxx> wrote: ... > I've sent out [1] > > [1] > https://lists.fedorahosted.org/pipermail/crash-catcher/2014-July/005535.html ... A good first step would be to draw up a list of ARBT bugs that we feel are critical for the Workstation user experience (this one [1] immediately springs to mind.) We should also ensure that any critical issues have been reported. It would be fantastic if someone could take this on. Second, we (or I...) need to do a design review to see where we are and where we want to be with regards to the problem reporting user experience. There is a lot of background material that we can draw on here [2]. Once we've done these two steps, we'll be in a position to have a constructive conversation with the ABRT team. There is also a more general issue here: traditionally, the Fedora release process has had a fairly limited definition of what constitutes a blocker, and there isn't a huge amount of downstream bug tracking in the run up to a release. If we want to raise the quality of the overall workstation experience, we'll need to expand the range of issues that are tracked for each release to include more general user experience bugs. This might well require changes to the workstation release process, as well as new release management roles. Allan [1] https://bugzilla.redhat.com/show_bug.cgi?id=1050154 [2] https://wiki.gnome.org/Design/OS/ProblemReporting -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
