Quoting Morbus Iff <morbus@disobey.com>:
experience if the user has more than a handful of "Other" modules. Shouldn't the user see a grouping for Taxonomy for all of the modules dealing with Taxonomy?
No, because that is a category. That is not a package. Please see the archives of the development list for an already extensive discussion of this, specifically my own message here, which inspired this docs:
To you it is a package but to the end user looking at the menu it is a category or package grouping; a module is a package; more than one module focused on extending the same function is a package group. The end user experience is what matters, not the dev types that know what it is supposed to represent.
http://lists.drupal.org/pipermail/development/2006-November/021080.html
Yes, I have read your technical explanation before. It is the end user experience I am trying to benefit. I agree that a module in a package, package grouping, category or what ever it is needs to move to Other if there is only one in the grouping installed in the users environment. I disagree that if I have more than one Taxonomy module package installed that the menu should display both of those in the Other package grouping rather than the Taxonomy package grouping. Earnie