I am really in favor for a central place for MMBase applications.
[X] I prefer one CVS module 'applications' with a sub-directory for every (non-core) project
In don't really mind if they are going to be stored in separate cvs modules or in one.
Gerard is working on a document that describes what kind of modules/software parts we have.
e.g.:
- MMBase core
- MMBase applications
- 3th party applications
The first two software parts should be provided by the developers community. The 3th party applications can be supported by a foundation.
If we know that we want to have a structure like this, we can easily create a new cvs module which contains the MMBase applications (The one with the MMBase core we already have).
So in my opinion you can just make the MMBase applications cvs module. just my thoughts,
greetings Rob
