In T12810#228939, @ognarb wrote:

The GenericName is not displayed in store only the summary in the AppStream file. The fact that the kde.org/applications doesn't use the Summary is because they are mostly too long.

In T12810#224120, @jriddell wrote:

Thanks for looking at this. Do you have any example patches ready to see if we can get some committed?

I gave this some more thought and I think I found a fundamental issue with updating these descriptions.

Hello, with this, would it be possible to assign ScrollMethod and ScrollButton?
Currently, mice such as the Trackman Marble, which I use, require a xorg conf file in order to allow scrolling with the trackball, both for xinput and libinput.
On Wayland it even requires a dbus command in order to activate this functionality, as mentioned by former KWin dev Martin.

So I was taking a look on Invent projects (like kdiff3 and labplot) to see where these short descriptions are stored, since it's a fairly straightforward process to send short, one-file MRs. Am I correct in assuming the changes I must do should be in the GenericName section of the .desktop file and nowhere else?
If so, what happens to the translations? If I just change the original GenericName, will e.g. GenericName[pt_BR] show up as fuzzy for translators?

A process is only insurmountable if it is not adequately documented

Removed hints

I think those appeared accidentally when I was testing how it would look like if the label text was shown as a tooltip for the Compression Quality label, I'll remove those and test it.

Hello, I think the text "Device" after the device name is too English-specific. It would be tougher to translate to many left-to-right languages since most do possess a structure like "Device: DeviceName" but not many have the "DeviceName Device" inversion.
The solution I see would be a heading, which is unfitting to how the KCM currently looks, but this is solved by having a separate page like Noah mentioned.

I'm a huge fan of Activities, so this is an interesting thought experiment, especially if I disregard the merit of removing Activities or not and jump straight to how it would work.
First off I'll start mentioning how I usually define Activities to make them easier to grasp:

Thanks Paul! I'll try to follow your guidelines. I'm not experienced as an editor or marketeer so please criticize if there's criticism to be made, after I start working on these long descriptions.

I don't particularly see any issue with creating a keyboard shortcut for restarting Plasma as long as it's very hard to press, so either a 3- or a 4-key combo. I directed merrit to ask here so the community can voice their opinions on this.
SDDM for instance already proposes a loginctl unlock-session command in case something goes wrong with it, so a fallback plan (though in a different context) isn't unheard of in Plasma.
The only issue with such an implementation would the hypothetical setup of plasmashell --replace in combination with kwin_x11 --replace, which would make such a keyboard shortcut more complex to set up since users might be on Wayland and kwin_wayland does not have a --replace flag and thus cannot be restarted without logging out. If possible, however, this would work better than a mere plasmashell --replace.

As an end-user, I usually get frustrated when I search for a tool on Discover and most results do not differ significantly either by name or description due to how generic they are; that's the case when you want to search for a utility that's available on multiple DEs. You have to click on each instance on Discover and read the long description in order to determine which DE it belongs to. An example of this is when you search for file managers. This is particularly bad with GNOME and GNOME-based (MATE, Cinnamon) applications, while XFCE does it generally well.

In T11976#223178, @ltoscano wrote:

In T11976#223167, @thiagosueto wrote:

Added Docs as a subscriber since if I'm not mistaken appstream descriptions are Docs stuff too.

Uh, afaik not exactly, no.

Should I remove Docs then? Also, is this managed individually by each application?
Since

The short descriptions task is basically complete.
Please provide feedback on my suggestions.
IMO, short descriptions are a task very suited for Promo to make applications more attractive, so feedback on this "marketing" should help as well.

Added Docs as a subscriber since if I'm not mistaken appstream descriptions are Docs stuff too.
Moreover, I'd like to ask: where are those descriptions located (which files, where in Phabricator etc) so I can send patches to change those?
Never sent a patch before, and I'd prefer doing it through the Phabricator web interface if possible.

I'll start working on the lengthy descriptions in a few days.

Okay, I think aside from Windows and OSX, we already have most major DEs and keyboard-driven environments here, and it's been a while since we had input from other people. Part 1 of section Tasks to be done in order to achieve this is already quite significant. I'll continue working on that, but that does not hinder discussion here, to be clear.

In T12281#213611, @aayushvats wrote:

Hey guys, i tried to make a poster.
does it work for you ?

Assigned myself to this specific task since I'll keep track of activity to put on the table.

Added T12423 as a subtask, it serves for organization. If you're interested in a specific project or want to work on a project but still don't have your name assigned there, you may add yourself easily to the table by editing the task.