Posted by sirtet on December 13, 2011 at 11:02pm
I am relatively new to drupal, and i've been evaluating some Module-types like lightbox- or imagecropping- Modules.
There are quite some comparison pages, and even a list of them.
Very usefull.
But i think as static text, they will always be outdated.
So, did someone ever think about dynamic comparison tables for modules?
I'd imagine a view that can pull compatibility, installs, activity etc. directly from the projects, so they would never outdate...
Maybe that's harder than i think?

Comments
Could do...
I don't think it would be terribly difficult to pull together automated information on the number of sites the module is installed on, how many recent commits there have been, or compatibility with core Drupal version -- all of that is available from the module pages. Although I don't know how much of that information is available to Views (we can make Views on drupal.org).
But even that sort of automated page would be outdated soon, because someone would come out with a new Lightbox module and it wouldn't be on the page. Also, I think some of the comparison pages have details that would be tough to automate -- at least I would hope so (an awesome comparison page I think should have some information from someone who tried out the module and offers some evaluation?).
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon
sure, this could not replace
sure, this could not replace manual testing and comparison, but it would help some.
I'd like to try if something useful is doable.
I think I read once somewhere that an anonymized copy of d.o. With user data can be obtained somehow, to do local testing of new features...
is that right?
how would that go? Could not find it again in a quick search.
Here's the link
http://drupal.org/node/1018084
You'd need to start by filing an issue in the Documentation issue queue (if you didn't already) in the Infrastructure component. Please also tag it with the "docs infrastructure" tag, so people interested in documentation infrastructure can find it and watch the progress, test out your page, etc.
Then you can request a d.o copy, following instructions in that link above.
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon