Inconsistent Naming?

Module Manager isn't totally accurate, but it sounds good, and it should be close enough to make sense to most users. Obviously, you could also just stretch it out to Module and Theme Manager, which doesn't sound quite so neat. Maybe Upgrade Manager or something like that...

If you decide to change the name, wouldn't it be simpler to start with the Drupal 7 version?

As for the name, I think the problem isn't really with Plugin Manager, it's with Drupal, which doesn't have a clear and clearly-defined name for this category (Drupal.org uses 'Downloads', but that's so general that it will lead to further confusion; and perhaps 'Contributions', but that's even worse)

Before the drupal security team shut me down and sent me over here ;), I had a module that did much the same thing, called "Installator". I think the name has a nice ring to it....

I would name it just 'Module Manager', doesn't matter that it can handle themes also. Because naming it 'Module Manager' would make it more popular and accessible to most of drupal users - both for discovering it for the first time through d.o and even for regular using it is more easy when names more expectable. Who cares so much that it can also handle themes, let it be nice surprise, a 'side feature', or even submodule - after all it's primary function is managing modules (at least most of the users want this feature).

I myself found it just by chance, i would never think to search for keyword 'plugin'. So lets rename it to 'Module Manager' and to be faithful to truth include in very beginning of description include clear note that it handles both modules and themes. Maybe 'Theme Manager' submodule would make it more easy to find it for those who are looking for theme manager and more easy to disable theme management feature for those who doesn't need it (i am using my customized themes mostly).

I think making it more popular would contribute to faster module development because of more testing, user input, contributions, and after all maybe even sponsorship.

What others think about this perspective ??

P.S. and for renaming it i think it may be not so easy, because you already have got 'plugin_manager' namespace for it, which reflects even in module url in d.o and i think in many other places. I feel that it can be nescessary to create new module and in old module give clear message that it is discontinued in the favour of the new module with link to new place. Also marking all releases in old module as no longer supported may attract attention of ppl using the current module to get news about new module and upgrade to it. Of course it is just my speculations a user perspective - i don't have any module created and maintained. Strategy for such changes should be figured out from documentation and with advice of developers.

I agree the name has to explain what this module does, as Joshua said it install's/update's/remove's modules. While "Module Manager" isn't an incorrect name it's hard to know what this module does just from reading the name.

I do however think "Module Installer" explains the 3 things we want to say install/update/remove. It may not directly say "update" but the process of updating a module is installing a new version so I certainly think it implies it better than "Module Manager".

But anything is better than Plugin Manager :)