Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E9E0417.60702@maniatis.org>
Date: Wed, 19 Oct 2011 09:56:23 +1100
From: Aristedes Maniatis <ari@maniatis.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111012 Thunderbird/8.0
MIME-Version: 1.0
To: dev@cayenne.apache.org
Subject: Re: Apache CMS migration
References: <4E9D81F8.2040806@gmail.com>
In-Reply-To: <4E9D81F8.2040806@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On Wed Oct 19 00:41:12 2011, Dzmitry Kazimirchyk wrote:
> Just started work on wiki site migration to the Apache CMS. Confluence migration tools provided with it are quite helpful, I've managed to create site template and convert few pages with their help.
>
> Also I read somewhere in the CMS docs that infra can setup staging area for us where we can try new CMS. If this information is not outdated I think we should ask infra to do this to be able to test the CMS more closely. If anyone has any suggestions or can provide any assistance with this, that might be helpful.
>
> Or I can open ticket in their Jira, asking them to create staging area for us, myself. In this case we need to decide where new site files will be situated (suppose something like cayenne/main/site/cms). Once we make decision on this I'll commit initial directory tree for the CMS there and infra will be able to setup staging for us.
>
> Thanks,
> Dzmitry

I think that cayenne/site/cms sounds like a good path. Not sure if we 
need the main. And yes, open a ticket in Jira since I think that's the 
way to get them to set up the staging site for us.

Ari

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A