Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of hepabolu@gmail.com designates
 64.233.170.194 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding;
        b=tG/G6AqoZT1/yvjJVUv8vhSPS/BQLliPgy+HztV2mXU/pApTTAywuQO9dmey/UWpcZDIWKwfLcovzD1qwxGUMxwJetGDVQBBy80Di79XUbTxNIsVB+IcGgjG7nqyfaoVCkc6d8eECgcn+RjRjk0fNlg7FARwYGLwA8XFznXZEaA=
Message-ID: <4300B2B3.8030201@gmail.com>
Date: Mon, 15 Aug 2005 17:20:19 +0200
From: hepabolu <hepabolu@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: [VOTE] Website update process
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Guys,

I don't know if a vote for this is required, but I'd like to have 
consensus/feedback, before I do something drastic.

As written earlier today there are gaps in the current version of the 
website, e.g. FAQs are missing. What I'd like to do is restore the 
current content of the website ASAP, BUT using Daisy as the source.
This comes down to the following steps:

- compare current Daisy content with counterparts in SVN BRANCH and 
update Daisy accordingly (I'll do this)
- update Daisy with missing content (i.e. the missing pages from the 
website) (me)
- do a Daisy-to-Forrest export (Ross?)
- update the website as described on the wiki 
(http://wiki.apache.org/cocoon/CocoonWebsiteUpdate)
Note: all stays as it is now, navigation, content etc.
- when the website is correctly generated:
   - remove all documentation from BRANCH (me)
   - remove all identical pages from TRUNK (me)
   - move all remaining documentation pages from TRUNK to Daisy, marking 
them for TRUNK

WDYT?

Bye, Helma