Jean-Marc Orliaguet wrote: [snip] > that is precisely what adds value to the project: designing an > Enterprise Content Management also means thinking about how to best > organize and to convey information, it is not simply about writing code. > If there are no collaboration spaces (apart from the mailing list) to > exchange ideas, to present sketches, design patterns, to put > documentation... how is this suppose to work? I don't know, ask the Linux kernel developers? :) Anyway, I'm not debating the need for a CMS eventually, and collaboration spaces are valuable. I'm just debating the need to put that on the list of requirements now. (besides this I am also worried about the possibility of 'dead' collaboration spaces, such as the Zope 3 wiki, but that shouldn't stop us from employing technology, just make us do it carefully and not spread ourselves too thin) Anyway, let's add a new requirement: the collaboration space for ECM should not be tied into the collaboration space of other projects. Regards, Martijn
Hosting: Nuxeo: Zope service provider