Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <429399BC.6000109@odoko.co.uk>
Date: Tue, 24 May 2005 22:16:44 +0100
From: Upayavira <uv@odoko.co.uk>
Organization: Odoko Ltd
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Planet Cocoon license and reuse of docs
References: <42926BDD.5030307@apache.org>
	    <a753b7f8050523170757537c0c@mail.gmail.com>
	    <4292F581.9070806@apache.org>
	    <50426dde3ead00eaad8f0134d59071b7@apache.org>
	    <ea5b94e3d4eb6e66eb5808c7b2e37c12@efurbishment.com>
	    <4293198C.4090806@apache.org>
	    <a753b7f80505240706441586fb@mail.gmail.com>
 <4293451B.0@apache.org>	    <a753b7f8050524082859094ef8@mail.gmail.com>
	    <42934F48.9030807@apache.org>
    <a753b7f805052409213d4abced@mail.gmail.com> <4293902F.80908@apache.org>
    <429391B7.9090805@odoko.co.uk>
 <45972.10.0.0.1.1116969279.squirrel@ags01.agsoftware.dnsalias.com>
In-Reply-To: 
 <45972.10.0.0.1.1116969279.squirrel@ags01.agsoftware.dnsalias.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Antonio Gallardo wrote:
> On Mar, 24 de Mayo de 2005, 15:42, Upayavira dijo:
> 
>>Sylvain Wallez wrote:
>>
>>>Sebastien Arbogast wrote:
>>>
>>>
>>>>The second important thing I notice in your remark is the argument
>>>>that people here know Cocoon but not PHP. But it's exactly our point :
>>>>we don't think Cocoon documentation should remain between Cocoon
>>>>developers and that's also why we chose a PHP based CMS : because
>>>>people are used to it, to its structures, to its customs. Right now
>>>>it's much more natural than any Cocoon-based solution. We consider
>>>>that documentation should not be written by developers and read by
>>>>users... everybody should be able to participate in the same effort
>>>>according to its own skills.
>>>>
>>>>Last but not least, our objective is precisely to make documentation
>>>>writing completely independent from the unerlying technologies, so
>>>>nobody should need to know neither Cocoon nor PHP to write
>>>>documentation (yes a little bit of Cocoon should be useful if one
>>>>wants his content to be useful but... you got my point)
>>>>
>>>>
>>>
>>>I'm sorry, but this is plain bullshit blabla to ease the pain of not
>>>using our own dog food.
>>>
>>>Cocoon is used by some huge content management systems all over the
>>>world. And it wouldn't be suitable to manage its own docs? People will
>>>laugh at us and go away.
>>>
>>>Sorry, I currently lack time to read this thread in full details, as I'm
>>>currently giving a Cocoon training to people writing a huge
>>>document/content management system... with Cocoon.
>>
>>Yes, but is it the job of someone who is interested in writing docs to
>>actually write a CMS at the same time? This seems like a bit much to ask.
>>
>>If someone else can offer an existing CMS that has the features they
>>need, and can be installed and operational within a reasonable amount of
>>time, then we'd be asking different questions.
> 
> 
> With the new apache zones, I think there is posible in a rasonable amount
> of time (hours?) to setup a CMS to do the job.
> 
> WDYT?

Then someone should do it, and we will see where that takes us. I'll 
volunteer for the part of doing any document conversions that might be 
required.

Regards, Upayavira