Martijn Faassen wrote: > Hi there, > > I'd just like to make my opinion clear on the topic concerning z3 base > versus svn.zope.org versus svn.nuxeo.com versus somewhere else. > > In this process, I've seen the people who happen to be hosting source > code in their own, company-controlled repositories, make this line of > argument rather often: > > "We cannot host ECM on your open z3 base, because z3 base doesn't have > X, and we really need X for ECM, and gosh, only our own > repository/website right now has this feature. Of course *if* your z3 > base would offer this feature we're entirely open to moving over to it!" > > For features you could fill in 'Trac', or 'copyright assignment > policy', or 'a powerful CMS which has workspaces' or whatever. > Martijn, 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 want to be able to put images, animations, concept maps online, publish information without having to hack some HTML code each time with 'sftp'. everyone is focussing on the svn, this only concerns the code... regards /JM
Hosting: Nuxeo: Zope service provider