Over on the 2.0 themes thread we've said we'd look at separating the core modules from other extension modules, what would this look like?
As an initial strawman to discuss how about separate folders for each group of related modules including all their tests and samples. So there could be a core folder that would contain most of the minimal modules we're currently bringing in stage 1 along with all the related itests, vtests and samples relating to those, a webservices folder which has all the binding.ws and wsdl related modules, and folders for each other extension type or other sets of related modules we might have. Although like that the samples are grouped within their related extension folder that doesnt necessarily mean thats how they need to be structured in the binary distributions we make. That build structure makes it easier to develop and build functional areas, in the distribution we could move them about wherever we like to make it easy for users. Is this the type of thing others are thinking of? ...ant
