The idea is to create core module which will collect modules usage statistics - list of installed modules of the site, list of active modules - both core and contribs, may be some other stats like OS and webserver (of course site owner must have options to disable sending any parameters if him prefer to stay anonymous), and regulary send this statistics to drupal.org. Here second part of module will analyze collected data and put them on web for public access. This way we get automatic feedbak of popularity of different modules, it help developers and contributors to decide which modules more popular and needs more attention and so on. May be contributors will contest with which other for high positions of their works in rating? - Anyway I think such statistics will add to development little drop of fun :)
This mechanism used for example in Debian project (debian.org) in package popularity-contest. Data collects automatically and sent by email to central server, this help to project developers prepare CD-sets of distro based on popularity of programs.
Comments
Comment #1
Bèr Kessels commenteddifference from debian is the fact that an installation != users.
We should not only get statistics on amount of installation, but also general stats of the sites using them, in order to have sensible data. Will administrators find this an infringement on privacy?
My suggestion, is to use an XML document for this. The site can provide an XML doc with all the details on http://thesite/drupal/sitedetails
Drupal.org can then parse that data.
This can replace the /sites system, and also provide a very good framework for help and support.
Comment #2
axel commentedYes, it very close to current sites directory, offered by drupal.module. But extended with some additional info. Of course, more attended sites should has more weight in statistics - may be offer it as optional feature? Anyway even statistics about modules usage will useful thing. I agree, all that may be realized as extensions of drupal.module and I reassign this issue to it.
Comment #3
axel commented> difference from debian is the fact that an installation != users.
In Debian we has the same situation - it may be installed on large multiuser server, but maybe installed to singlusered notebook. In case of site task even simplier, because website is public thing and we may analyze public info about it from search engines - and by such indirect facts make opinions about him popularity.
Comment #4
dwwthis has been fixed via http://drupal.org/node/39697. i don't know why no one noticed this older issue back when they were working on that. normally, we use the oldest reported issue, and mark later copies as the duplicates. oh well. additionally, there are proposed changes to the project module to take advantage of this new data via http://drupal.org/node/66013 and http://drupal.org/node/66015. given all of that, i'm just going to close this issue, since it's either already implemented, or more specific tasks have been submitted to the right places for the remaining functionality.