I am in the early stages of developing a group of modules that will be inter-dependent and will ship as a single downloadable project. This has got me thinking about avoiding module namespace conflicts for submodules that ship as part of other module packages.
At present there would be nothing from a technical standpoint to prevent someone from creating a module with a name of views_ui as there is no views_ui directory in CVS. My proposal is that Drupal.org have a policy that when a module developer includes a submodule within their main package, they are encouraged to create a project with the name of the submodule that contains only a README.txt file, directing the reader to the main module. This will ensure subsequent module developers do not inadvertently commit a project that will lead to module conflicts for end users.
Comments
I Agree
I think this is a good idea. It seems ideal to me for this to somehow be automated from the .info file of the submodules since they already include a "project" element in the file.
Please also see Download link for missing module for a good reason to add this.
www.allisonmission.com
tentmaker.allisonmission.com