After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 497810 - add "Evolution FAQ" menu item; improve user-visible dialogs
add "Evolution FAQ" menu item; improve user-visible dialogs
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Shell
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-18 06:12 UTC by André Klapper
Modified: 2013-09-13 00:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (3.70 KB, patch)
2007-11-18 06:14 UTC, André Klapper
rejected Details | Review
patch (2.91 KB, patch)
2007-11-20 12:22 UTC, André Klapper
none Details | Review
okay. this one works :) (2.91 KB, patch)
2007-11-20 12:26 UTC, André Klapper
committed Details | Review

Description André Klapper 2007-11-18 06:12:19 UTC
this will avoid all those useless "can't send mail, please help" bug reports. people should use support forums for instead for such stuff.
Comment 1 André Klapper 2007-11-18 06:14:19 UTC
Created attachment 99270 [details] [review]
patch
Comment 2 Srinivasa Ragavan 2007-11-19 04:18:42 UTC
Andre, I still think that we shouldn't remove it, instead educate them to file  better reports. Can we think innovatively to see how we can make the user file a better one? May be a dialog to tell what not to do with a 'Don't show this again' check? Or something else...

FAQ thing is awesome. No doubts :)

CC'ing other guys for a second opinion.
Comment 3 Matthew Barnes 2007-11-19 20:43:13 UTC
Maybe add some verbage to the Bug Buddy dialog clarifying what the feature should and should not be used for.  Would apply to all applications, really.  That would require a change to bug-buddy itself, of course.
Comment 4 André Klapper 2007-11-20 10:01:11 UTC
@mbarnes:
we already have too much text in bug-buddy that is read by nobody. example: we warn users that the submitted data may contain confidential information, and that users should review the data they are going to submit. nevertheless reporters complain about stuff that was submitted.

(In reply to comment #2)
> instead educate them to file better reports.
if that is meant for real, then you may rewrite 90% of the error strings. look at firefox and why they are successful - if i can't reach a website, it tells me possible reasons in the error message, in a language that even my parents would understand. it tells me what *I*, the user, can do. evolution's messages are often cryptic and technical (you studied CS? then they are no problem, of course).

okay. here we go, let's rewrite the error messages and dialogs. i should collect my favourite bug reports in the next weeks, stuff like "can't send mail" or "don't work". otherwise i will probably stop triaging the non-crasher reports as well.
feel free to query bugzilla for evolution bugs with status whiteboard "errormessages". i collected some of them already.
Comment 5 André Klapper 2007-11-20 12:22:35 UTC
Created attachment 99393 [details] [review]
patch

only adds the FAQ menu item.
sometimes it does not work for me at the first try, so testing the patch appreciated!
Comment 6 André Klapper 2007-11-20 12:24:01 UTC
uargh. wait...
Comment 7 André Klapper 2007-11-20 12:26:07 UTC
Created attachment 99394 [details] [review]
okay. this one works :)
Comment 8 Milan Crha 2007-11-20 18:36:23 UTC
I agree with srag to keep there that menu option. Maybe hide it more, or if they open it, just show a message about what they can and what they cannot do with it, so some of them will reject to fill useless bug reports. It will be just for Evolution, no change in bug-buddy.

I agree with Andre that there is too much text in bug-buddy. None wants to read it, they just want help a bit (at least send a crasher) and then get it second chance. I saw many bugs without "What were you doing..." text.

I'm not sure if comparing firefox with evolution is good idea, at least you have there a page, not a dialog, which describe the problem. You know, the text in a page looks really different then huge error dialog.

Anyway, I agree to improve error dialog texts, but it's not a work for coders, it's work for language-educated people/users (Users will write, users will understand.) Some kind of error dialogs with most common advices can help, even sometimes can be totally odd. It really depends on an error type - so no generic messages, but specialized for "each" error code we consider as worth better explanation. Maybe something like this?
Comment 9 Srinivasa Ragavan 2007-11-21 04:37:51 UTC
Andre, I'm all for rephrasing/correcting error dialogs. If anyone wants to take this, and suggest/post better messages, it can be taken in. I'm sure that it anyway needs to get better once the non-intrusive things are in as it uses a lot from those dialogs.

Comment 10 Srinivasa Ragavan 2007-11-22 05:25:15 UTC
Anyways commit this for 2.21.3
Comment 11 André Klapper 2007-11-26 19:53:46 UTC
patch committed to trunk: revision 34589.
Comment 12 André Klapper 2007-12-08 15:39:00 UTC
i should have seperately filed a tracking bug about improving user visible strings earlier: bug 502515. please comment, or add dependencies, or ignore.
Comment 13 Matthew Barnes 2008-03-03 13:04:23 UTC
Is this still an open issue or can this bug be closed?
Comment 14 André Klapper 2008-03-03 15:50:00 UTC
fixed, closed, thanks.