Hi Jan I was discussing this with a few people and we have come up with what we feel would be a better proposal in the long term, that is to populate the group tag from the desktop file category shipped with the package. There are many advantages to this which I will get to but first i'll cover the fact that not every package ships a desktop file, in the end I think this is mostly a positive, the whole point of this mechanism is user discovery and there is a bunch of things such as libraries and devel packages that users shouldn't want to discover with groups we have package management for that. Similarly someone is unlikely to choose a virtualization hypervisor based off searching groups. The one placed I can think of where some people might want some form of groups is for certain command line applications like editors etc if people want they can add a desktop file and set it not to show in desktops. The most obvious benefit is this is a system we already expect people to maintain and its really obvious if its wrong. It also means that we are not depending on 1-2 people to check everything and keep it right because if you get sick or go on a holiday or decide to do something else there hasn't been much indication of others willing to step up and keep the groups running, its likely they will just fall out of maintenance and disappear. It also has the advantage of well defined classifications that are shared across all parts of the distro such as desktop menu's etc, beyond that they are also generally shared across distro's for the most part again adding to the consistency. Between the "Standard" and "Technology" Categories it likely also has most of the info that you've suggested you want to include in tags. So again I want to propose we drop the Group: from spec files and then move toward auto generating it from relevant desktop files as possible which will be much more maintainable and will save every one work (especially as its already been demonstrated that we have tools capable of dropping the group flag. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B