I'm thinking about a database which is storing:
- Project name
- Download file
- Module name
- Date
- MD5 and SHA1
- Module description
- Drupal Version
- README.TXT or INSTALL.TXT
and programming an interface (module) to check these against your own installation.
What I need is to download all "[PROJECT].tar.gz" files and import these into a database. This was the easy job (simple devel example).
Currently this is done with a CCK designed table, but I will switch to an own node-type cause of some CCK restrictions (e.g. search).
the next two steps are writing:
- a repository browser (client side)
- a repository manager (server side)
A full featured application should be able to:
- Search modules from inside your Drupal installation
- Download manager for modules
- Check for newer versions of modules
- Installation manager for modules
- eMail notification about new modules
- and so on
That's my basic ideas. If anyone has suggestions or critics: Post please.
Comments
New Contribution System
narres, are you aware about this? http://drupal.org/node/77562
There seems to be some overlapping.
Daniel F. Kudwien
unleashed mind
Daniel F. Kudwien
netzstrategen
I recognized before
, but as I allready started I will continue my develoment in a silent way ;)
"classifying and presenting"
I'm less interested in more sophisticated management of module installation at this point, and more interested in being able to pick the right ones to begin with.
The bland naming conventions for Drupal modules combined with overlapping feature sets can make it very hard to know what to use. Image? Image Assist? Images? Image Assistant? Upload Images? Image Uploader? Upload Assistant? I exaggerate (slightly) but you see what I mean.
I would love to see a more complete system for presenting modules, similar to the Joomla Extensions area. Heck, theirs is great -- maybe we could just use it?
Though the new tabs help a bit, our modules area is still crying out for the subcategories, searchability, user ratings & reviews, download counts, last updated dates, feature comparisions, etc. that are common to most software repositories.
And unless more creative and memorable module names are used, the attachment of some kind of thumbnail, logo or screenshot image should almost be mandatory. When everyone in the room is a Jim, James, Jack, John, Joe, or Jeff, I'm more likely to remember faces than names.
I'm not a programmer, just a user, so my ability to help is limited to suggesting features and functionality. (i.e., please copy Joomla's system...)