Mis-categorized modules

thanks for creating this issue. i've got a few more suggestions. i'll just keep posting them here as i come across them. here's the first:

why does the "developer" category only include 1 module (that's not devel.module!), when most of the things that were discussed on the list as developer-specific are in the "administration" category? seems like either we should do away with the "developer" category entirely, or we should do a better job pulling things out of administration into developer. here's a partial list:

• devel
• simpletest

"CCK" should be in "Content" ;)

"UserSwitcher" should probably be in "Development", too (assuming we're going to keep a separate category for that).

"Volunteer" should probably be in "Events".

Personally, I have never liked the "Developer" category, because it's not a category that describes the module's function, but it's intended audience, and that's not necessarily helpful.

I quite like the "Developer" category. Especially since modules can have more than one category, so it's not a limitation.

OK, if we're going by function lets change 'Developer' to 'Development'

signup is only in "events" not "modules" which screws up all sorts of things. isn't there some way to automate it so that all modules get in that category automatically? thanks.

The right way to do this is to re-vamp project so that it uses separate vocabularies -- e.g. associate N vocabularies with project -- Drupal, Modules, Translations, etc.

Drupal would contain the terms:
* Drupal
* Drupal.org
* Documentation
* etc.

Modules would contain the categorization and be set to required and multi-select. Probably a better use of time to implement it this way than try and munge the way hierarchical assignment works -- we get this "for free" by using the built-in taxonomy features.

(And yes, I know this is late in the game to be suggesting this, but I thought I should list the Right Way if someone is going to put time into it....)

There is relevant help text that should display at node/add/project_project, but doesn't. I know it's not everything, but it would help.

I've opened a new issue: http://drupal.org/node/57667

browsing by name shows about 20 modules that start with the word "taxonomy". there are only 4 entires in the taxonomy category. ;)

"Article" is inside content. It should rather be in "content displayed".
--> Too much modules are falsely or confusely named. Usually, this was the Drupal user that complained that finding a module was a pain. Now, administrators have difficulties to correctly assigned them to categories... ;-)

Boris, Nedjo: i think the problems you're talking about are fixed now that http://drupal.org/node/64221 has been committed and installed on drupal.org. please comment there if you have further ideas on how it should work.