From easyant-dev-return-22-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Thu Feb 17 19:53:02 2011 Return-Path: Delivered-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Received: (qmail 49953 invoked from network); 17 Feb 2011 19:53:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 19:53:02 -0000 Received: (qmail 43923 invoked by uid 500); 17 Feb 2011 19:53:02 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 43904 invoked by uid 500); 17 Feb 2011 19:53:02 -0000 Mailing-List: contact easyant-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: easyant-dev@incubator.apache.org Delivered-To: mailing list easyant-dev@incubator.apache.org Received: (qmail 43896 invoked by uid 99); 17 Feb 2011 19:53:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 19:53:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeanlouis.boudart@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 19:52:58 +0000 Received: by gwaa12 with SMTP id a12so1263323gwa.6 for ; Thu, 17 Feb 2011 11:52:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=x8iBoQ6/bto3AeMljoZJZxzK9ySwcaw6lmYQjnHajqY=; b=i+goE+qhhG/yNiOcwrdGFl6E4YYhg7qrGRWbfXvmvQCwTlv1bFQXAf41iuJqkX2xgY T9fcvd3f9ktbotuNlQbPfsWh3A0gd3Qgagi3rRyEoVPAxYIgjPnmdu+NzVcSVUgONw0h OtMdQSrgCLe5jXD/CZtBNPuit1e++aqoYkAcw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KkbLdTp71QRfL60c6X8YA3lB2VzPBqrCm6AsxJWHwHEloXypp4Cz/5gh2CvHJHoGwe /ycFcoOpqf8FD0rLY4Dg+yNQTAl3tg+Z7D/HUYExG8Kd+wGlZlaS0axQPEOg6NVUH4a3 DlFvwFG5LE3oJ9DjAlRbMClR5ebXoNZXp24cY= MIME-Version: 1.0 Received: by 10.42.240.197 with SMTP id lb5mr3505629icb.25.1297972355972; Thu, 17 Feb 2011 11:52:35 -0800 (PST) Received: by 10.231.59.209 with HTTP; Thu, 17 Feb 2011 11:52:35 -0800 (PST) In-Reply-To: <06075F83-CC34-4B3C-8523-65E20F6743BC@hibnet.org> References: <06075F83-CC34-4B3C-8523-65E20F6743BC@hibnet.org> Date: Thu, 17 Feb 2011 20:52:35 +0100 Message-ID: Subject: Re: The website From: Jean-Louis Boudart To: easyant-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf30549af534c041049c7fbddd --20cf30549af534c041049c7fbddd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I was also in favor of using Xooki as we already use it for documentation. We already have a xooki plugin for easyant that can handle history a la ivy= . By the way i don't know enough Apache infrastructure to know how we could deal for publication and how to enhance the publication workflow. Reading your description here seems to highlight that Apache CMS would be easier to maintain / use. Le 17 f=E9vrier 2011 18:49, Nicolas Lalev=E9e = a =E9crit : > As one of the first steps, I think we should setup a web site. > > Then comes the question about the tool to use. > > I am in favor of using xooki, since the current documentation is also bas= ed > on it. We could also imagine using the Apache CMS for the site, and xooki > for the doc. > > The pros for the Apache CMS is that it is well supported by the infra tea= m. > It has a build-in notion of staging website: get some preview before goin= g > live; here is the example of the main asf staging site : > http://www.staging.apache.org/. Something nice too is that we only need t= o > edit the templates, the building and committing of the actual html files = are > delegated to a buildbot. Last but not least, once build, the doc get onto > the staging or the production websites in few seconds. > Interesting links about the CMS: > https://blogs.apache.org/infra/entry/the_asf_cms > > http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-w= ebsites/ > http://www.apache.org/dev/cms.html > http://www.apache.org/dev/cmsref.html > > The pros for xooki is that is can manage the tree of content of the > site/documentation (see the tree on the left on the Ivy site: > http://ant.apache.org/ivy/). I think this is a important feature. Then > about build and deployment, lots of manual steps. You'll have to build > things locally, and commit them yourself. Then go to people.apache.org an= d > do a svn up there. And wait few hours to finally get it online. > We use that process for both Ivy and IvyDE website. I'm trying to find a > way to improve this, working a have a quite similar process to the Apache > CMS one. This change is also needed because the infra team is willing to > depreciate people.apache.org for website publishing in favor of the Apach= e > CMS. But I didn't find a way yet to use xooki within the CMS workflow. > > I'm in favor in choosing xooki, betting that I'll find a way to deal with= a > better workflow. > But if I fail the site will have to be migrated to the CMS, which might b= e > some piece of work. > > WDYT ? > > Nicolas > > --=20 Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org --20cf30549af534c041049c7fbddd--