ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #10827
Re: Reviews and bug reports
On Thu, Dec 18, 2014 at 12:04 PM, Sam Bull <sam.hacking@xxxxxxxx> wrote:
See my proposal for the feedback app. If we use a webapp that uses UOA
to login to launchpad, then the support link for the app can be
handled
by the webapp and open straight to the bug reporting page for that
app.
First, there is no support link right now; there's only a bare URL.
Even if that's fixed (and from what I know of scopes, this may be
harder than it seems), it won't be obvious to users that they can
report bugs there. And even if it is made obvious, it's still more
work than submitting a review. My argument distills to this: It should
be as easy to submit a bug report as a review. Any plan that involves
more than filling out a single text box and hitting "Send" fails this
metric.
On Thu, Dec 18, 2014 at 12:16 PM, Rodney Dawes
<rodney.dawes@xxxxxxxxxxxxx> wrote:
I think Launchpad's bug reporting page is simple enough and tries to
catch duplicates.
I disagree and think the magic "try to catch duplicates" feature is
broken and adds complexity to the problem.
As a technical user, I like the duplicate detection, since it means I
don't need to do a separate search before I submit a bug. For
non-technical users, at whom my feature is aimed, I agree that it's a
problem.
On Thu, Dec 18, 2014 at 12:13 PM, Dave Morley <davmor2@xxxxxxxxxxxxx>
wrote:
That wouldn't work, most commercial vendors won't know anything about
LP won't care about LP and certainly won't use it.
From what I can see in the Android store, for example, getting lots of
good reviews is paramount. Why wouldn't vendors take advantage of a
system that allows them to shunt poor reviews (i.e. bug reports) into a
different silo where most people won't see them?
Few apps are developed by IBM. Most seem to be due to individuals or
small teams. Such people will be nimble enough to enable LP bug
tracking if they see an advantage in it.
Anyway, let's not use future hypothetical problems as an excuse to
avoid fixing current real problems.
The homepage/contact url in the app details page should be sufficient
As I've just argued, it isn't. We already have a problem, and the only
users are those with the technical ability to install a new OS on their
phone. It's only going to get worse once actual Ubuntu devices go on
sale.
What do other app developers think? Am I the only one having this
problem?
Robert
Follow ups
References