Re: Web links integration in applications: bugs, translations, help...



ahoj loïc,

Am Montag, den 26.11.2007, 13:32 +0100 schrieb Loïc Minier:
>  Distros, just like GNOME, have bug trackers, forums, support systems.
>  GNOME and some distros have translation infrastructure.  These are
>  usually not integrated into the end-user applications.
> 
>  For example a new user wanting to report a bug against Gedit would:
>  1) fire his web browser to lookup where to report bugs
>  2) open the relevant bug reporting page, look for the Gedit component
>  3) file the actual bug description and details
> 
>  You can imagine the process is the same for translations fixes / new
>  translations, help requests in forums, etc.
> 
>  Step 1) and 2) could very well be skipped would we integrate an URL
>  link in each application "Help" menu (or a bug-buddy
>  launcher).  That is, selecting "Help > Report a bug" would bring you to
>  the relevant bug reporting page for this application, on your
>  distributor's bug tracking system (or at GNOME's, freedesktop's, etc.
>  depending on who the build comes from).
> 
>  Ubuntu has been doing such an integration with a system called "LPI"
>  (Launchpad integration), and I think it's a generally useful concept
>  which could be used by other distributors and by upstream apps. [1]

>  How do other people feel about such a system?  Would it make sense to
>  integrate this in GNOME?

afaik evolution and anjuta have such functionality already implemented.
there's advantages (easily see where your software sucks) and
disadvantages (get lots of "can't send mail" bug reports from evolution
users that aren't willing to read the how-to of their mail provider, and
even if you answer them by asking a few questions you will not receive
an answer again in 90% of the cases, so i waste a lot of time).
if we'd have some kind of dialog, explaining the difference between an
error in a piece of software (-> bugzilla) and a misconfiguration/RTFM
case (-> support forum), i'd be more pleased with it. but users tend to
not read dialogs, see bug-buddy: even if you tell people to take a look
at what they are going to send, they still complain if a password gets
submitted in the bug report.

perhaps a better approach: educate the user by improving the error
strings in the software. there's always room for improvement:
http://aloriel.no-ip.org/uploads/2007/08/error_de_evolution.jpg .
i love firefox because of explanations that even my parents would
understand, if they'd touch computers.
but currently, 30% of non-crasher evolution reports are already "can't
send mail. please help" reports, because of the "Submit Bug Report" menu
item. i have the feeling it will become more. ;-)

andre

various links to discussions about this issue:
http://bugzilla.gnome.org/show_bug.cgi?id=497810 and
http://blogs.gnome.org/aklapper/2007/11/18/too-popular-too-buggy-too-easy/

-- 
 mailto:ak-47 gmx net | failed
 http://www.iomc.de/

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]