We have a unique situation in that we're creating extension/theme combos. Unfortunately because they are an XPI, there is no way to have them listed as themes in amo. There should be a way with amo to designate that something should be crosslisted in themes if it is both a theme and an extension.
Hm, I am not sure about that. IIRC, currently a theme is considered to be only a "skin" for Firefox. The instant it adds functionality, it's an extension. Of course, it's a fuzzy line (are fancy UI effects "functionality" yet?), but I am unsure if it would help the user to expect installing a theme (only) and realizing they changed not only the look of their browser but also added extension functionality. In other words: What's so bad about having your extension marked as such?
(sorry for the component confusion, I think this is a policy discussion first, and if approved would turn into an implementation thing)
I think is WONTFIX as well. Something is either a theme or extension. Sure, there are extensions that can skin parts of the browser. But unless something is listed as a theme in the add-ons manager, it's not a theme. For example, Personas is definitely an extension, even though it lets you quickly theme your browser.
The problem is that it is a theme and an extension. So if people are looking for themes, they don't find them. What we'd like is for our themes to be discoverable when people are searching for themes. The problem is the search is based on things in the theme category not things that include the word "theme" And disagree with the assertion that things are extensions or themes. We have built a scenario where a theme and an extension are bundled together, so it offers both. I consider it a theme that comes with an extension, not an extension that comes with a theme.