cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject Re: [PROPOSAL] Cocoon-apps CVS module
Date Fri, 09 Aug 2002 14:03:04 GMT
Ivelin Ivanov wrote:

>Andy,
>
>----- Original Message -----
>From: "Andrew C. Oliver" <acoliver@apache.org>
>To: <cocoon-dev@xml.apache.org>
>Sent: Friday, August 09, 2002 7:31 AM
>Subject: Re: [PROPOSAL] Cocoon-apps CVS module
>
>
>  
>
>>Hi Ivelin,
>>
>>In the near future I plan on donating this:
>>http://www.superlinksoftware.com/cocoon/samples/bringmethis/
>>along with documentation on the pieces of it, why they were used, "best
>>practices", etc.  The intent is for this to serve as a
>>"pet shop example" minus the recent connotation.  I hope others will
>>help refactor it into *best* practices, etc.
>>    
>>
>
>Will be nice to have as an app.
>I like the app separation idea. I am only concerned with stretching the 2.1
>release too far.
>  
>
Which is WHY we need to have the cocoon-apps area, so that we DON'T 
stretch the 2.1 release too far.
Besides, I've been working on this since BEFORE 2.1 started, and all of 
the work I'm doing for 2.1 is to
support this effort.

>  
>
>>Now, do I think this should be CLOSELY associated with Cocoon (read:
>>docs featured on the website, stored
>>on apache.org, YES)
>>
>>Do I think it needs to go in the xml-cocoon2 module?  Not necessarily.
>>
>>Do I hope to be a committer of cocoon-apps?  Absolutely (it will be a
>>pain in the a** for anyone else to keep up with the patches to
>>the bringmethis reverse auctions example).  Do I think that should make
>>me a committer to xml-cocoon2 module?  No.
>>
>>So while I understand your concerns, I think we need this BECAUSE
>>documentation is a priority for Cocoon.
>>
>>Secondly, look at the new cocoon documentation wiki:
>>http://outerthought.net/wiki/Wiki.jsp.
>>
>>Notice the activity!  Its been DAILY!  And already I think there are
>>several better examples of how to configure the sitemap
>>than in the Cocoon doc body.
>>    
>>
>
>
>Is the final goal for the content to make it in the main doc site?
>
yes.

>If so, then it's a good staging board.
>I hope it does not evolve on its own and in parallel with the main docs
>without synchronization between the two.
>  
>
Think of it as the "documentation content production area" (And if you 
notice its VERY successful so far).

-Andy

>
>
>Ivelin
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>  
>




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message