Thank you Greg, i tought it was just internal information for developers. Anyway thx. Mac -----Original Message----- From: Greg Knaddison - GVS [mailto:Greg@GrowingVentureSolutions.com] Sent: Monday, March 12, 2007 10:51 PM To: development@drupal.org Subject: Re: [development] Downloaded modules stats On 3/12/07, Maciej Perlinski <maciej.perlinski@meant4.com> wrote:

Hi there i remember i ve received once the email with all statistics for downloaded modules, where can i find this information i m pretty curious about our module download stats.

A quick google search will show that you can get different information from various sources: http://www.google.com/search?q=drupal%20download%20statistics I did some analysis of the January data: http://knaddison.com/drupal/january-drupal-download-statistics You can get the full details from that page or from Craig's sandbox: http://cvs.drupal.org/viewcvs/*checkout*/drupal/contributions/sandbox/craig/ misc/downloads_jan_2007.htm?rev=1.1 Previous to that there were others who did analysis of similar and other datasets. Regards, Greg

On 3/12/07, Earl Miles <merlin@logrus.com> wrote:

It would be pretty cool if we could script your analysis so that we can just dump the awstats data into it every month.

The analysis is basically a spreadhseet I made that contains a lookup table of all modules, themes, and translations and has some reference data for them. I copy the entire awstats data into that and do a "text to columns" on it. Then I have a few functions that parse out the filename and the version from the filename (e.g. so that trip_search-5.x-1.2.tar.gz and trip_search-5.x-1.1.tar.gz are both labeled as the "5" version of trip_search). And then I manually do a handful of pivot tables to aggregate the data and see which items are most popular. I'll send that to anyone who wants it. I believe the last time we discussed more automated solutions we got stuck at the best implementation. If we inserted a counter between the link on the project page and the ftp server we would have easy data collection into drupal database, but lose some people who get it directly from FTP. If we use awstats output then we get basically everyone but miss folks who pull from CVS directly (which probably isn't statistically significant - especially not now with the new release system). Awstats also has the problem of scripting something to parse that data. I believe dww was in favor of the awstat->project solution and Dries in favor of the "In project.module solution" http://lists.drupal.org/archives/development/2006-11/msg00264.html There are even issues for some of these things http://drupal.org/node/66015 - browse by popularity http://drupal.org/node/52475 - Display usage data for projects http://drupal.org/node/79550 - Automate gathering of quality metrics (though it's kind of a meta issue and should probably be split) I'd love to work on some/all of those, but have lost my round tuit. Maybe I'll find it at Drupalcon ;) Greg

I found this post and wondered if this is still relevant to Drupal.org, and if so, what can we do about it? http://drupal.org/node/47915 Nice post, webchick! -Robert

On Mar 13, 2007, at 5:09 PM, Greg Knaddison - GVS wrote:

I believe dww was in favor of the awstat->project solution and Dries in favor of the "In project.module solution"

some how this issue escaped me in the run-up to my vacation in february, but behold: http://drupal.org/node/102422 someone *else* actually provided *code* for project.module to enabled download counters on all project releases. ;) needs reviews and testing, but the basic approach is there (a new column in the {project_release_nodes} table for the counter, a DB update to add it, and the download links point to a menu callback that increments the counter, then redirects to the actual downloadable file). of course, this will miss any time folks have direct links to ftp.osuosl.org (which we tend to do for core a lot in the sticky front page stories about the latest security fix, for example). that's why i'd rather just get the stats from ftp.osuosl.org directly, and have a script to parse that data and stuff it into the DB. but, i suppose the kind of counter implemented in #102422 is better than nothing (and would probably be more useful to non-d.o sites using project_release.module, anyway). anyone interested in this topic is encouraged to take a look at that patch, try it out on a local test site, etc. furthermore, please consider working on all this project quality metrics stuff for Summer of Code: http://drupal.org/node/128546 thanks, -derek (dww)