One of the most annoying aspects of working with the modules overview is the (admittedly) dilemmas of categorising modules, leaving a bunch of modules either in the Other category, or in completely strange places, to "my logic". And everyone has their own little logic, which is why we cannot expect to agree on "one" logic.
This is an opportunity for this module. First as a nice and practical feature, but actually even more interesting if it were made in a way that could provide Drupal.org with statistics of the main preferences of "most users of this module".
Imagine letting us override which category (or even more than one per module..!?) each module should be shown under, on the settings page of this module, and then, as the update status module connects to Drupal.org to get new release info, it can offer to submit the names and categories only of the modules that have a custom category set. That could be used on drupal.org to make better decisions related to categorisation.
Then we dont need to take on an eternal discussion about module categorisation on drupal.org, but just use the statistics that tells us what "most" admins mean about the categorisation for each of the modules on their own (multiple) sites installs.
Comments
Comment #1
Leeteq commentedComment #2
aohrvetpv commentedUser-defined categories is an interesting idea, but I think this feature request may be outside the scope of this particular module. The modules overview at admin/modules, where modules are grouped by package, is provided by the System module. The purpose of this module is to provide advanced settings for the Update Manager module (update.module, formerly known as the Update Status module). Update Manager is not responsible for the admin/modules page. Update Manager provides admin/reports/updates and the other tabs there.
Comment #3
aohrvetpv commentedI understand now that you are suggesting to transmit project categories information along with the updates checking, in which case this would relate somewhat to Update Manager functionality. However, it seems like this information could also be transmitted independently of Update Manager. Doing so would probably be simpler than piggybacking on Update Manager requests.
What you are proposing would require server-side drupal.org support. Practically it might be easier to set up an independent website that makes user-supplied categories information available. Then, if it is a successful feature, it could be incorporated into drupal.org--sort of like how popular contributed modules get merged into core.
Just my thoughts, take them for what they are worth.
Comment #4
Leeteq commentedOoops, sorry, when I replied to the related issue, I was in that project queue, but when saving this feature request that is only referencing that other semi-related issue, I forgot to change the project.
This suggestion was meant for https://www.drupal.org/project/module_filter module, which is the correct place for this feature request.
Moving it over there.
BTW, I am not suggesting to add (more) dependency on either the update function in core, or drupal.org server support. My suggestion is to to make it available first locally on each site, then as a technical possibility to turn on receiving such category information later. First get people to start using it, so we have some basis for statistics collection, and then we can use this as the basis for a new feature request for drupal.org. I dont want this feature request to be stalled pending some approval from drupal.org maintainers. Make it independent and local-only first.
Comment #5
smustgrave commentedClosing as outdated after 8 years as we transition to Drupal 10.
I'm keeping an eye on the 7.x branch of this module, reviews and majors, but active work is going toward 4.x (supporting D10)
If valid for 4.x please reopen