Feature #13299
Make WhisperBack easier to find in the GNOME Overview
100%
Description
WhisperBack can be run like all applications: search for the beginning letters “wh” and it’ll appear.
However, I think that WhisperBack might need some metadata so that when users search for “bug” or “report” or “tails”, they will also find the software in the Activity overview.
The affected file is data/whisperback.desktop
in https://git-tails.immerda.ch/whisperback/.
Files
Subtasks
Related issues
Related to Tails - |
Duplicate | 2016-08-06 | |
Related to Tails - |
Resolved | 2016-08-22 | |
Blocked by Tails - |
Resolved | 2018-03-22 | |
Blocks Tails - |
Resolved | 2018-03-09 |
History
#1 Updated by Anonymous 2017-06-30 13:30:07
- related to
Feature #11621: Document how to run WhisperBack from the Activities overview added
#3 Updated by intrigeri 2017-06-30 15:43:47
- Subject changed from Improve WhisperBack packaging metadata to Improve WhisperBack launcher metadata
- Description updated
- Status changed from New to Confirmed
- Type of work changed from Debian to Code
(It’s in the upstream source rather than in the packaging.)
#4 Updated by intrigeri 2017-06-30 15:44:06
- Starter set to Yes
#5 Updated by Anonymous 2018-01-19 10:35:40
- Subject changed from Improve WhisperBack launcher metadata to Improve WhisperBack launcher Appstream/packaging metadata
#6 Updated by sascha.markus@gmail.com 2018-03-26 21:54:33
Patch with added keywords
#7 Updated by intrigeri 2018-03-27 08:58:43
- Assignee set to anonym
- Target version set to Tails_3.7
- QA Check set to Ready for QA
Thanks for the patch!
#8 Updated by intrigeri 2018-04-13 11:38:29
- Assignee changed from anonym to intrigeri
#9 Updated by intrigeri 2018-04-13 16:14:04
- blocked by
Bug #15440: Missing WhisperBack 1.7.14 in Git added
#10 Updated by intrigeri 2018-04-14 07:39:18
- Subject changed from Improve WhisperBack launcher Appstream/packaging metadata to Make WhisperBack easier to find in the GNOME Overview
- Status changed from Confirmed to In Progress
- Assignee changed from intrigeri to sajolida
- % Done changed from 0 to 20
- Type of work changed from Code to User interface design
Hi Sascha & sajolida!
I’m sorry we should have made it clear earlier that some UX design was needed first to get the terminology right.
So, typing in the GNOME Overview seems to search both in the Comment
and Keywords
fields.
- regarding
Comment
: I don’t think it’s displayed anywhere so we can write whatever makes sense to us; I don’t particularly like the proposed change e.g. our terminology is “error” and not “bug”; I suggest keeping the original string and focussing on theKeywords
to make it easier to discover WhisperBack from the Overview - regarding
Keywords
:- I’m all for adding “feedback” and “bug”
- if we add “reports” I think it should be singular
- adding “tails” is consistent with our other custom apps so it makes sense to me
- I would also add “error” because that’s our user-facing terminology
sajolida, what do you think?
#11 Updated by intrigeri 2018-04-14 07:39:39
- blocks
Feature #15392: Core work 2018Q2 → 2018Q3: User experience added
#12 Updated by sajolida 2018-05-02 11:33:35
- Assignee changed from sajolida to sascha.markus@gmail.com
- Target version deleted (
Tails_3.7) - QA Check changed from Ready for QA to Dev Needed
Keywords proposed by intrigeri:
- feedback
- bug
- report
- tails
- error
I have nothing to add.
Note that this improvement still assumes that people know that WhisperBack is what they want. For example, if I open the activities overview and type “bug”, I will only see WhisperBack and its icon. But I won’t know what WhisperBack is about because the name “WhisperBack” doesn’t tell it to me. I would have to guess and try to open WhisperBack anyway and understand what it does from its interface.
A solution to that could be to rename WhisperBack as “Error Reporter” or something like that but it’s clearly outside of the scope of this ticket. I think that would go in the direction of replacing custom application names with generic names describing what they do “Nautilus → Files”, “Palimpsest → Disks”, “Evince → Document Viewer”.
If anybody else likes this idea, tell me and I’ll create a separate ticket.
Sascha: Do you want to prepare another patch that uses the original Comment and the list of keywords proposed by intrigeri?
#13 Updated by sascha.markus@gmail.com 2018-05-02 18:32:43
Sure, here you are.
- the comment is the same as in the original git version
- report is singular
- error is also in the list of keyword
#14 Updated by intrigeri 2018-05-03 06:26:21
- Assignee changed from sascha.markus@gmail.com to intrigeri
- QA Check changed from Dev Needed to Ready for QA
#15 Updated by intrigeri 2018-05-05 14:16:08
- Target version set to Tails_3.8
#16 Updated by intrigeri 2018-05-05 14:16:21
- Type of work changed from User interface design to Code
#17 Updated by intrigeri 2018-05-07 12:01:42
sajolida wrote:
> A solution to that could be to rename WhisperBack as “Error Reporter” or something like that but it’s clearly outside of the scope of this ticket. I think that would go in the direction of replacing custom application names with generic names describing what they do “Nautilus → Files”, “Palimpsest → Disks”, “Evince → Document Viewer”.
>
> If anybody else likes this idea, tell me and I’ll create a separate ticket.
Sounds good to me!
#18 Updated by intrigeri 2018-05-07 12:02:59
- Target version changed from Tails_3.8 to Tails_3.7
- % Done changed from 20 to 90
- QA Check changed from Ready for QA to Pass
Looks good, will apply once Bug #15440 is fixed. Hopefully this will make it into Tails 3.7.
#19 Updated by intrigeri 2018-05-07 12:39:28
- Assignee changed from intrigeri to bertagaz
Merged, will be fixed once bertagaz releases a new WhisperBack!
#20 Updated by bertagaz 2018-05-10 11:05:09
- Status changed from In Progress to Resolved
- Assignee deleted (
bertagaz) - % Done changed from 90 to 100
intrigeri wrote:
> Merged, will be fixed once bertagaz releases a new WhisperBack!
It’s been released!
#21 Updated by sajolida 2018-05-15 17:06:48
- related to
Feature #11689: WhisperBack: Enforce 70 character limit on the user written messages added