Stefano wrote: > In short, instead of a competitive tagline 'use Cocoon instead of J2EE > or .NET' (which would eventually emerge out of a Cocoon Pet > Shop demo), > we should do something different 'no matter what you what to do with > your web, Cocoon will help you doing it better'. [please, excuse the > shitty marketing tone, but we are talking about vapor anyway] > > Those are my thoughts.
I second this: we shouldn't be competing with Struts, J2EE, .Net, and a gazillion other web frameworks out there. And before we have *really* conquered the flow/webapp domain, we should focus on our strengths, i.e. XML-based web publishing. I'm quite sure the Flow & Form people out here will help Cocoon transition into the webapp space, but we are not there yet. And as far as sexy web pages is concerned, we should remember that Apache is a community based on collaborative *source code* development, where good solid code and relevant documentation is more important than marketing-savvy web pages :-) If I find some time during the summer months, I'd like to start something in the line of http://httpd.apache.org/docs-project/ for Cocoon, built on top of Forrest. I was pretty impressed with the WebWork documentation (http://213.203.18.31/), we already have a lot out there, but it should be re-structured and made more accessible. </Steven> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
