> From: Steven Noels [mailto:stevenn@outerthought.org]
> 
> John Morrison wrote:
> 
> > >
> > >     - deciding on URL-namespace design
> >
> > We could have 'test' or 'temp' as prefixes for development and decide
> > on the actual ones later...
> 
> What I actually meant was structuring the URL (name)space as in:

I know, I ment we could use:

>     http://xml.apache.org/
      http://xml.apache.org/test/
>     http://xml.apache.org/projects/cocoon/
      http://xml.apache.org/test/projects/cocoon/
>     http://xml.apache.org/stats/downloads-per-project/2002-02/
      http://xml.apache.org/test/stats/downloads-per-project/2002-02/
>     http://xml.apache.org/about/whoweare/
      http://xml.apache.org/test/about/whoweare/
>     http://xml.apache.org/news/xerces-2002-02-06.xml
      http://xml.apache.org/test/news/xerces-2002-02-06.xml

until we'd settled on the final ones :)

> etc etc
> 
> Making the equation between resources & views, too.
> 
> >
> > >     - Forrest 'core' itself: C2 sub-sitemap + related materials
> > > (stylesheets
> > >     et al.)
> >
> > I think this is best - keep the cvs repository small.
> 
> OK, so we need some deployment scripts to move the forrest webapp inside
> a blank Cocoon instance. Now if only this blank instance would be part
> of the build targets of Cocoon...

Stefano, David and I (I don't know about Sam) have commit access to
Cocoon - I'm sure, given the right patches ;) - we can make this happen :)

J.

PS - have you cvs write access yet?

> > >   - what the different project teams need to do to get their
> > > project listed
> >
> > A location in their cvs which forrest can access? (really
> > should finish
> > reading before I speak :)
> 
> Naah, my suggestions/alternatives aren't rocket science, neither :-)
> 
> </Steven>
>