What's your idea?
All module maintainers to define related projects on projects.
Use this data to populate the "Related projects" block using these and any back links from other projects "Related projects" fields grouped by # references and order # ref descending.
If none found, then fallback to the automated one.
What are the benefits?
To actually make this block useful.
Two existing examples that show the maintainers suggestions beside the related projects block.
Menu Node API - https://drupal.org/project/menu_node
Safeword - https://drupal.org/project/safeword
Added benefits are likely to include:
- Easier to locate the right module for the job
- Potentially reduce number of duplicate projects / sandboxes.
What are the risks?
Potential for invalid related projects.
How can we measure the impact of this idea? (metrics)
Who directly benefits from / will use this improvement? (target audiences)
Site builders
Module maintainers
Are additional resources available for discovery/implementation? (volunteer effort, financial backing, etc.)
I could probably find the time to do this if someone gives me a feature export of the project content type. :)
| Attachment | Size |
|---|---|
| drupal.org-related-projects-block.png | 14.45 KB |
| drupal.org-related-projects-block-2.png | 13.38 KB |
Comments
Related issue
There was a previous issue about how to improve this block:
https://drupal.org/node/479812
Right now it's mostly useless, your suggesting would definitely be an improvement.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide
"mostly useless" is a pretty
"mostly useless" is a pretty bold claim when that particular block was designed/developed with a rigorous analysis to ensure it is useful: https://drupal.org/node/323106
Letting people edit the data is proposed in https://drupal.org/node/479812 (which I see mgifford has already commented on).
Seems like a solid idea to mix with the automated recommendations.
knaddison blog | Morris Animal Foundation