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 748197 - Guidelines about error messages
Guidelines about error messages
Status: RESOLVED OBSOLETE
Product: gnome-devel-docs
Classification: Applications
Component: hig
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-devel-docs maintainers
gnome-devel-docs maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-20 16:10 UTC by Alexandre Franke
Modified: 2021-07-05 10:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexandre Franke 2015-04-20 16:10:37 UTC
There's nothing on error messages in the HIG. Can we have guidelines on what is preferred between "Cannot…", "Could not…", "Failed to…", etc. for a bit more
consistency?
Comment 1 André Klapper 2015-04-20 20:50:34 UTC
Similar topic: Using the word "kill" (e.g. a child process).
Comment 2 GNOME Infrastructure Team 2021-07-05 10:53:26 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-devel-docs/-/issues/

Thank you for your understanding and your help.