Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <48290.136.8.152.13.1115389829.squirrel@webmail.paiwastoon.com.af>
In-Reply-To: <42777DFF.5010008@upaya.co.uk>
References: 
    <17012.136.8.152.13.1115126160.squirrel@webmail.paiwastoon.com.af>
    <42777DFF.5010008@upaya.co.uk>
Date: Fri, 6 May 2005 16:30:29 +0200 (CEST)
Subject: Re: Updated Dev Guide -> Avalon (see bug #34696)
From: "Torsten Schlabach" <tschlabach@apache.org>
To: dev@cocoon.apache.org
Reply-To: tschlabach@apache.org
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

Upayavira,

>> If you can't work out what to do, just ask.

Apparently I do NOT have write access to the Cocoon SVN. At least I don't
manage to get my commit through. I had never tried the Cocoon SVN before,
I just picked up the info that all Lenya committers had access to Cocoon
as well from a dicussion somewhere else. Apparently this isn't true for
all Lenya committers.

Could you please be so kind and check the page in?

Regards,
Torsten

> Torsten Schlabach wrote:
>> Hi folks,
>>
>> I have recently updated the page about Avalon. The original version is
>> here:
>>
>> http://cocoon.apache.org/2.1/developing/avalon.html
>>
>> The patch is filed unter bug #34696.
>>
>> I am not sure what the procedure is. I think I have write access to the
>> Cocoon SVN because I am a PMC member of Apache Lenya, but I think it
>> would
>> be sort of unpolite at least to just go ahead and check this in as I am
>> not a committer in Ccooon.
>>
>> So would anyone review this documentation patch and apply it or give me
>> feedback?
>
> (moved do dev list, doc list is now just for wiki notifications)
>
> It is certainly polite to ask(!), but I'm happy for you to commit this
> page. However, as we are in the process of creating docs for 2.2, we
> need to have something in the trunk repository, so that your changes
> don't get lost.
>
> So, if you're able, also commit something to
> cocoon/trunk/src/documentation/src/content/xdocs/
>
> Name it c21-avalon (which means that it is a straight copy from Cocoon
> 2.1, and hasn't been updated to Cocoon 2.2).
>
> If you can't work out what to do, just ask.
>
> Regards, Upayavira
>