> The problem is complex, there are different types of > problems. But maybe we could add it as an introduction to > this document.
Yes, it is a complex problem with a lot of wild ideas behind it. An introduction to the problem would be welcome. > > MMBase is a good example of these systems. Well known 'open source' > > ones are wiab and didactor. > > (where can I download this one?) Well, that is one of the issues this docuemnt could solve. Wiab had a site when it was developed by Framfab (www.framfab.nl/wiab). Finalist hasn't made a public site (yet) about what wiab is at the moment and what it will be in the future. The near release version 2.5 of Wiab is under MPL License. We don't have the code public available, but we will share it on request. I don't know if this will change in the future. Some small space on the mmbase.org website where people can find some info would be effective. I don't know what the intentions are for Didactor. The only thing I know is taht several paries deliver server facilities for the project. Didactor might be a good example of an application which needs a public secure cvs to develop it by multiple parties.. > > Examples of pieces are editors, editwizards, security > implementations, > > remote cloud communication, workflow, polls, forums, chat, > and email. > > IOW, the power of MMBase is that it does not limit the > system to the > > features which it provides. The weakness is that you always have to > > integrate pieces on the engine which takes time and knowledge. IMO, > > the first outweigh the second. > > > > For this integration we need (a) tool(s)..... The integration I meant is that you add pieces togehter and write code to couple them. For example, when someone publishes a node in the workflow you want the node te be copied to a remote server and an email to be send to the author of the node. This involves integrating workflow with remote communication and email. It is hard to create tools who can do that. It is only possible when everything has a well-defined interface. > > A next step might be to provide server facilities (cvs, mailinglist, > > webspace) for pieces/systems build by people on different > locations. > > This step is almost like what apache and sourceforge are. The > > difference will be that the systen has to add value to the MMBase > > community to get the facilities. People building those don't > > necessarily have to be a core commitor of MMBase. > > Yes, that's why I think we need different groups of > commitors, like apache has. Mentioned in the other post, not everyone at finalist wants to become a core-commitor of mmbase with all the responsibilities to add their contributions to the community. Different groups of commitors has my +1 Nico Klasens Finalist IT Group Java Specialists
