DrupalCon Baltimore: 161 sessions, many voices, infinite possibilities. Earlybird rate ends Friday.
When browsing drupal's current list of add-on modules, the list is extremely lengthy, and hard to browse unless you know what you're looking for. I'd like to suggest that project nodes have dependencies. For example, for the cck module, there are a lot of sub-modules (email field, url field, etc), it would be good if we could get those out of the current list of modules, and on the cck project page as a list, because they do the user no good without the cck module.
Of course, there are some projects that are only useful as dependancies, and the other projects should be listed on the Modules page anyways.
Maybe projects could either be marked as a "library" for other projects, or a subproject of a project, instead of dependant... I'm just throwing some ideas down.
|#152||projectinfolog.txt||13.25 KB||Owen Barton|
FAILED: [[SimpleTest]]: [MySQL] 328 pass(es), 112 fail(s), and 49 exception(es). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch project_info.CVS_to_git.patch. View
FAILED: [[SimpleTest]]: [MySQL] 349 pass(es), 117 fail(s), and 70 exception(es). View
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 102102-project-info_25.patch. View