On 14 September 2016 at 10:44, Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: >>>>>> "RC" == Ralf Corsepius <rc040203@xxxxxxxxxx> writes: > > RC> IMO, it should be mandatory for Fedora maintainers to look into RH > RC> Bugzilla, because that's the product they are "maintaining" and what > RC> users are using. > > I disagree in general; when the bug volume exceeds a certain amount > bugzilla basically becomes useless. However, it would be really nice if > _someone_ looked at RH bugzilla for those packages and did something > with them. > > We used to have "bugzappers". What we really need is someone to do > triage and to forward bugs on to upstream when appropriate. This > obviously requires volunteers. > > I think this is an excellent job for someone who wants to help out. > Does Gnome have documentation on performing bug triage like our kernel > team does? https://fedoraproject.org/wiki/KernelBugTriage > > All volunteers would really need is accounts at the upstream trackers, > the will to search for duplicate bugs there, and some basic knowledge of > when to ask for more information and how to properly select components > upstream. I would imagine that a large number of the bugs that are > filed are duplicates of existing bugs anyway. > > Note that I sadly don't have any free time to actually help with this. > I've tried to do kernel bug triage, and it's very, very difficult and > time consuming. But that's the kernel; I would hope that just sorting > out Gnome bugs wouldn't be quite so bad. > It is just as bad for pretty much the same reasons: 1) Do you have access to that system. 2) Is the problem in the app or in X or in the kernel or the hardware. 3) If it is in the hardware is it a monitor/video card/motherboard issue 4) If you think it is in the kernel go to kernel triage 5) If you thinking it is in X follow the kernel triage but use s/kernel/X/ 6) If it is in the app can you even figure out what configuration caused it? 7) Is the bug really in the app or in some side app which it talks to? Normally you work backwards down the list but you have to cover all the bases as a good many crashes are from something you have nothing to control. Which is why various people find that they go to XYZ bugtracker and get told it isn't the distributions problem because it isn't the OS they used and they can't duplicate. [I am using XYZ because this problem can be generalized to Gnome/KDE/XFCE/Libreoffice/etc.] One of the reasons that bugzappers seemed to fall apart was it was a slog of work that burned out people without much in the way of reward because it never ends. The remaining bugzappers then took more of the load over and over again until you ended up with 1-2 people? Which is also happening with package maintainers. You get packagers with piles of packages burning out and the remaining people taking more and more packages over time. This ends up with people with hundreds of packages that they have under their belt and no way to actually keep track of the bugs on them. On the other hand, we have this conversation every (or every other) mid release cycle... so maybe we should just do the play one more time. Some drama about how Gnome sucks, gets special treatment, or isn't as special as systemd, is always put upon.. then a dramatic quitting around beta and general agreement that we will all do better for the next release. It's just like Shakespeare without iambic pentameter. > - J< > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
