> I was not sure what to do. It depends on what we want with > the applications in the distribution. > There are two options. > > 1. Make these applications fully active on the first start of > the release (setting module configuration files on active and > applications on auto-deploy). That means that for example the > community application will load and try to install it's builders. > > 2. Put all the needed files for these > applications in their appropiate configuration directories > but make them inactive. Their JSP's, the documentation and > the readme's in the release should point users to the > configuration files to activate the applications.
I think, the issue here is that the distro has 2 goals. 1 showing what MMBase is and how extendible it is (a webapp where you can hotdeploy new functionality) 2 starting point for developing customized webapps. The distro is now more suitable for 1 which makes it less for 2. The cvs repository is suitable for 2 Your option 2 sounds more suitable for 2. MMBase webapp implementors have a hard time to extract the desired files from the distro for use in their own webapp. A simple MMBase webapp only needs the MMBase core with the taglib (and maybe the editwizards). A more advanced one will probably use the cloudcontext security, email, media or rmmci application. The first three are not in the distro. I hope the 1.8 distro will address these 2 goals. Nico Btw will there be an 'official' update on this list about the plans for 1.8? On the last dev meeting we discussed that the 1.8 release will be a cleaning release with all the core projects on hold. If this still is the case it would be nice if everyone in the community knows this (not only the people who were at the dev meeting).
