Several taxonomy-related modules put themselves into package = "Taxonomy".
I suggest this module move there too and help keep "Other" tidy :)

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Reviewed & tested by the community

Makes sense.

joachim’s picture

joachim commented
Status: Reviewed & tested by the community » Fixed

Fixed in both 5 and 6 branches.

heine’s picture

heine commented

Please don't abuse package for this. The tendency of module authors to see package as some sort of category makes the admin/build/modules page on a medium to large site nearly unusable.

joachim’s picture

joachim commented

In what way unusable?
I'm developing a large site now, and I have 35+ modules in 'Other'.
Maybe in some cases categories are vague and meaningless, but there are a lot of modules out there (I'm running at least 5) that clearly do only stuff to do with taxonomy.

heine’s picture

heine commented

These are not categories, they are packages; a bunch of modules that are distributed together or depend on one an other.

This has been discussed over and over. See for instance http://lists.drupal.org/pipermail/development/2006-December/021348.html and http://lists.drupal.org/pipermail/development/2006-November/021080.html and the Writing info files documentation.

joachim’s picture

joachim commented
Status: Fixed » Active

Ok fair enough.
I'll roll it back -- but your only reason is "because the docs say so". That's a good enough reason for me -- but frankly your other reason about usability is rubbish.

And btw this is why I HATE mailing lists. How do I reply to those messages? I can't.

joachim’s picture

joachim commented
Status: Active » Closed (works as designed)

Rolled back on both branches, set to 'by design'.
But I think some way of organizing the admin modules page is required -- and most of the solutions mentioned on IRC the other day were way too complex and over the top.