On Thu, 2005-08-18 at 18:57 +0100, Ross Gardler wrote:
> Thorsten Scherler wrote:
> > On Thu, 2005-08-18 at 13:25 +0200, Andreas Hartmann wrote:
> > 
> >>Thorsten Scherler wrote:
> >>
> >>[...]
> >>
> >>
> >>>Lets startup small to have something to play with (like in every good
> >>>Las Vegas wedding, chips are on the house). ;-)
> >>
> 
> We have an unrelated thread on Forrest list regarding us trying to do a 
> First Tuesday event (devs meeting online to work on Forrest). The reason 
> I mention it here is that I see an opportunity.
> 
> It has been proposed that we use the Cooon wiki to take notes. I've 
> suggested that if Thorsten (or anyone lese for that matter) can install 
> a Lenya instance for us (either in the Lenya Zone or the Forrest Zone) 
> we can use that instead. The advantage is that it will get the Forrest 
> devs to use Lenya. The more people we can get to at least look at it the 
> more likely we are to get them to help with Doco.
> 
> So, can somene set this up for us before the first tuesday in September 
> (thats Sept. 6th).
> 

We have a demo add http://lenya.zones.apache.org:9999/index.html.

I reckon, gregor is right and we should use our doco branch for that.
The demo we can set up either @forrest or @lenya zones. I do not care, I
have permissions on both. ;-)

Anyway what you said is true and the recent discussion on the PMC lists
about commit access for all cocoon based projects (forrest, lenya and
cocoon committer) seems to make *really* sense. IMO every (based on)
cocoon committer should have write access to the doco-branch.

Tell me where should I set it up?

salu2

> Ross
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to