In #538904: D8UX: Redesign Modules Page → (and in other issues too) it's been debated how to group/sort modules best. One of the problems mentioned with the current way is that there currently is no easy way for users to predict under which package a contrib module will be located when it extends (or uses) two or more other modules (contrib or core).
Consider this edge-case, fictional i18n Taxonomy Views Panels Forum example project that requires core taxonomy and forum + the respective contrib modules mentioned in its name. Where do we list it? Surely not under Core, but should it be under i18n, views or panels? How about in all three places?
So, if the users expect to locate this module when they click the first relevant group they find while scanning the modules place (i18n, since they are listed alphabetically), then it'd be good practice to place it there by using package = Multilingual - Internationalization. If their list of modules is really long and they know that that the "Views" group is listed last, they probably won't even bother to scan the page and simply head to the bottom trying to see if our fictional module is there. So we might as well use package = Views. You get my drift?
Now, if we allowed multiple values, we could have:
package = Multilingual - Internationalization, Views, Panels
...and so the module would be listed in all these respective categories. There you go: no more users complaining about the number of clicks they have to make in order to locate such multipurpose modules ;)
Postponed: needs info
9.5
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There hasn't been movement on this in almost 10 years. Wonder if its request we can close out?
Since there hasn't been a follow up going on 2 years going to close out. If still desired please re-open