On Sat, Nov 07 2015, Maximiliano Curia <maxy@debian.org> wrote: > I support that approach for most cases, but it doesn't scale for teams like > KDE that have only a small number of maintainers, an impressive amount of > packages and a large number of reported bugs (and a tremendous amount of > pending issues that shows that we are not very efficient as proxies). Also, a > desktop environment can be used in many different ways, much more than the > ones we can cover, and having maintainers acting as a proxy for use cases they > don't really use or trying to follow a bug that they can't reproduce usually > ends in a waste of time. > > As such, I find it better to ask submitters that have an upstream request to > send the request upstream directly, they will provide better feedback and, in > general, have more energy available for solving the issue. > > If the submitter prefers not to send the request upstream we might act as > proxies, at least if we can reproduce the issue or understand the issue fully. I can understand how it would be difficult for maintainers of large numbers of packages, like the KDE team. I sympathize with that, and definitely appreciate your efforts. I still feel like there should be a better way, though. In order for me to submit a bug upstream to KDE I had to go through the process of registering with bugs.kde.org, and then submitting the bug, all after I had already submitted the bug to the BTS. Imagine every user going through this process to submit upstream bugs for all packages they use. It's a pretty high barrier, one that I'm sure most users would never bother with. Package maintainers almost certainly already have accounts with the upstream issue trackers for the software they maintain, so are in a much better position to file bugs upstream than the average user. Certainly the overall time spent on filing bugs would be greatly reduced if users only had to deal with the BTS, and package maintainers handled upstream forwarding. I guess the ideal would be an easy way for package maintainers to forward bugs upstream. It seems like this could somehow be scriptible, such that it's little more than the push of a button for the maintainer to forward a bug upstream. > Sure, the upstream bug tracker is a bugzilla bug tracker hosted in > https://bugs.kde.org, in order to submit a new bug you'll need to be signed > in, which means you probably need to create a new account. > > The "New" link at the top of the page starts the new bug submission process, > you'll need to fill the product (okular) component (Printing) and then fill > the rest of the fields as you see fit. It's okay to add the Debian bug url in > the bug description, but try to make the bug report self contained adding the > important pieces of information to the bug description. > > After submitting the bug upstream you could link a Debian bug to the upstream > bug using the debbugs forwarded command. But in this case a message to this > thread with the bug url would suffice. https://bugs.kde.org/show_bug.cgi?id=355005 Thanks so much for the attention, and for you work as maintainers. It's much appreciated. jamie.
Attachment:
signature.asc
Description: PGP signature