Talk:Modules

We should probably mention how modules are to be organized in the repository. Speaking of which...it'd be nice to have a standard README or similar metadata in a predictable location within modules in the repository so we can loop through them and display pertinent info (e.g., for an automated download page). We also should decide how modules will deal with versions/releases. Do we re-create module folders under /branches/ and /tags/ or do we allow each module to make /trunk/, /branches/, and /tags/ folders as needed? I guess I'd favor the latter. -Burke 15:30, 8 January 2007 (EST)

I was thinking the metadata/config.xml would suffice for this. The app that iterates over the uploaded modules simply has to look at the module name/version/author/description elements in the config.xml document. The second module version release is definitely the way to go. Its easily doable with subversion. Once we get some complicated modules that demand it, we can set it up. -Ben 15:36, 8 January 2007 (EST)