Comment 14 for bug 509389

Hi,

I would prefer a design discussion about this first. I'll add my idea of how it could be done.

Each plugin can belong to one or more categories. I think Categories is a fine name for it, but the implementation is more like tags.

Each plugin has a Categories: line in the plugin information. The categories the plugin belongs to are listed separated by commas. Each category is styled as a hyperlink; if you click on the link, the plugin list changes to show only plugins from that category (the filter field might change to 'tag:Categoryname').

A plugin has multiple category assignations so that we can cover desktops (GNOME/XFCE/etc) and functionality (Communication, File Management, Base Functionality) (for example). Categories are not a total description (i.e. each plugin has only a few categories).

If a plugin doesn't have a category, it is in the 'Application Specific' category (for example Virtualbox plugin or Truecrypt).

Category names are localized so they must be unique and plugins should not invent new.

I don't have so many patch comments at this point. "dunder" names such as __plugin_category__ are reserved by Python -- which means that we should perhaps not use any at all, but instead we only use dunder names that are established (__author__) or begin with kupfer (__kupfer_name__)