From easyant-dev-return-104-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Tue Mar 15 09:09:29 2011 Return-Path: Delivered-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Received: (qmail 76243 invoked from network); 15 Mar 2011 09:09:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Mar 2011 09:09:29 -0000 Received: (qmail 74649 invoked by uid 500); 15 Mar 2011 09:09:29 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 74624 invoked by uid 500); 15 Mar 2011 09:09:29 -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 74616 invoked by uid 99); 15 Mar 2011 09:09:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 09:09:29 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted sender) Received: from [216.86.168.183] (HELO mxout-08.mxes.net) (216.86.168.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2011 09:09:23 +0000 Received: from hibpro.anyware (unknown [84.14.163.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1C0F1509F0 for ; Tue, 15 Mar 2011 05:09:01 -0400 (EDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1082) Subject: Re: Website From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= In-Reply-To: Date: Tue, 15 Mar 2011 10:09:01 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3727B130-2242-44A9-B8D7-D26808845B55@hibnet.org> <840A9FDE-A4B3-401F-B7B0-9D4D6FA45D72@hibnet.org> <49D4720A-6D22-4B75-B909-D4A5B236081F@hibnet.org> To: easyant-dev@incubator.apache.org X-Mailer: Apple Mail (2.1082) Le 15 mars 2011 =E0 09:01, Jean-Louis Boudart a =E9crit : > While backporting changes from site to core documentation i was > wondering how to deal with common pages like FAQ, contact. > Should we keep thoses pages in both places ? > Focusing on contact pages, should we copy all the subpages (source > repository, issue tracking, irc, mailling lists ?) easyant doc vs easyant website is about offline vs online. I would say = that since our communication channel are all over the internet, it seems = pointless to duplicate the pointers to them in the offline doc. Nicolas =20 >=20 > 2011/3/14, Jean-Louis Boudart : >> Generated doc looks good for me ! >>=20 >> A few minor things to fix (it should not be blocking to go live) : >>=20 >> - footer's background image is too small, the last line (the 3rd = one) is >> not visible as we write in white color. >> - backport template.html styles and images to >> easyant/core/src/documentation to have the same layout between doc = and >> our >> website >>=20 >>=20 >> Le 14 mars 2011 15:41, Nicolas Lalev=E9e = a =E9crit >> : >>=20 >>> I have put the doc of the trunk into the website. I did some general >>> review >>> of the branding, broken links, it is now looking ok for me. >>>=20 >>> I have then generated the site into the production branch: >>> https://svn.apache.org/repos/asf/incubator/easyant/site/production >>>=20 >>> Please review the site before we get it live. >>>=20 >>> Nicolas >>>=20 >>> Le 13 mars 2011 =E0 18:39, Jean-Louis Boudart a =E9crit : >>>=20 >>>> Done, the download page is also OK. >>>>=20 >>>> After a quick review i think we could ask infrastructure team to = put it >>> in >>>> place. >>>>=20 >>>> What are missing ? >>>> Link to easyant documentation (svn:external pointing to >>>> src/documentation >>>> for example). >>>>=20 >>>> Le 11 mars 2011 16:23, Nicolas Lalev=E9e = a >>> =E9crit >>>> : >>>>=20 >>>>> great work Jean-Louis. >>>>>=20 >>>>> As an incubator project, Easyant website needs to follow the = Incubator >>>>> branding: >>>>> http://incubator.apache.org/guides/branding.html >>>>>=20 >>>>> So we nee to put a disclaimer in the home page and add the = incubator >>> logo >>>>> in the header. >>>>>=20 >>>>> Nicolas >>>>>=20 >>>>> Le 11 mars 2011 =E0 16:07, Jean-Louis Boudart a =E9crit : >>>>>=20 >>>>>> I've initialized a draft, we still need a download page linking = old >>>>> release >>>>>> before Apache Incubator. >>>>>>=20 >>>>>> Feedback are welcome >>>>>>=20 >>>>>> Le 9 mars 2011 13:42, Nicolas Lalev=E9e = a >>>>> =E9crit : >>>>>>=20 >>>>>>>=20 >>>>>>> Le 9 mars 2011 =E0 11:55, Jean-Louis Boudart a =E9crit : >>>>>>>=20 >>>>>>>> It seems that we can't have a staging website [1] except if we = use >>>>> Apache >>>>>>>> CMS. >>>>>>>>=20 >>>>>>>> Now comes a few questions: >>>>>>>>=20 >>>>>>>> - As we haven't really started our website, should we follow = our >>>>>>> original >>>>>>>> idea and use xooki to generate our website ? >>>>>>>> - Do we really need a staging website ? or can we live with = only >>>>>>>> production branch published "in live" ? >>>>>>>=20 >>>>>>> To my mind, I don't think a staging branch is that important >>>>>>> compared >>> to >>>>>>> the feature of having a template mechanism which nicely handle a >>>>>>> toc. >>>>>>>=20 >>>>>>> Nicolas >>>>>>>=20 >>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> 2011/2/28 Jean-Louis Boudart >>>>>>>>=20 >>>>>>>>> Looks good for me. I also think it would be great to have a >>>>>>>>> staging >>>>>>>>> website. >>>>>>>>>=20 >>>>>>>>> The process seems workable enough and can be handled by an = easyant >>>>> build >>>>>>>>> (playing with scm-svn, xooki plugin). >>>>>>>>> We can imagine having something like this : >>>>>>>>>=20 >>>>>>>>> - easyant publish-local : would generate local website >>>>>>>>> - easyant publish-shared : would generate the staging website = and >>>>>>>>> publish it >>>>>>>>> - easyant release : would generate the production website >>>>>>>>>=20 >>>>>>>>> I created an issue for this ( >>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached = a >>>>> draft >>>>>>>>> there :p >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Le 28 f=E9vrier 2011 11:34, Nicolas Lalev=E9e < >>> nicolas.lalevee@hibnet.org >>>>>>=20 >>>>>>> a >>>>>>>>> =E9crit : >>>>>>>>>=20 >>>>>>>>> Hi guys, >>>>>>>>>>=20 >>>>>>>>>> (most of this email is quite a duplicate of the one I have = done >>>>>>>>>> on >>>>>>>>>> ant-dev) >>>>>>>>>>=20 >>>>>>>>>> Finally I looked myself into how the Apache CMS works. >>>>>>>>>> So basically it is about having somewhere in svn the sources = of >>>>>>>>>> the >>>>>>>>>> website in markdown format. A buildbot job then takes care of >>>>> building >>>>>>> the >>>>>>>>>> html files and commit them into a "staging" branch. The = staging >>>>> branch >>>>>>> is >>>>>>>>>> published via svnpubsub to staging.apache.org. Then we can >>>>>>>>>> trigger >>> a >>>>>>>>>> merge of the staging branch into a production one. Another >>>>>>>>>> buildbot >>>>>>> build >>>>>>>>>> the html file and again a svnpubsub push it to = www.apache.org. >>>>>>>>>>=20 >>>>>>>>>> For thoses who don't know, svnpubsub is a tool developed by = the >>>>>>>>>> ASF >>>>>>> infra >>>>>>>>>> in order to have svn changed quite quickly and efficiently >>> retrieved. >>>>>>> The >>>>>>>>>> ASF infra is promoting it for website publishing. >>>>>>>>>>=20 >>>>>>>>>> For our needs, I think it would be great to have both a = staging >>>>>>>>>> and >>> a >>>>>>>>>> production branches, so there would also be a >>>>>>>>>> http://incubator.staging.apache.org/easyant/. >>>>>>>>>>=20 >>>>>>>>>> About having a buildbot to build the website, I don't think = it is >>>>>>> possible >>>>>>>>>> with xooki, as the current build around xooki is not able to = make >>> the >>>>>>>>>> distinction between a change in the template and a change in = a >>>>> source. >>>>>>> So >>>>>>>>>> the build doesn't know wether to build the changed files or = the >>>>> entire >>>>>>>>>> website. As the xooki generation is quite slow, if there is a = lot >>> of >>>>>>> page >>>>>>>>>> like in the Ivy site, it can takes ages. >>>>>>>>>>=20 >>>>>>>>>> But I think this is still workable with xooki. So what I = suggest >>>>>>>>>> is >>>>>>> having >>>>>>>>>> the following svn layout: >>>>>>>>>> * incubator/easyant/site/sources >>>>>>>>>> * incubator/easyant/site/staging >>>>>>>>>> * incubator/easyant/site/production >>>>>>>>>> And the process will be: >>>>>>>>>> * edit the xooki files in "sources" >>>>>>>>>> * locally launch a build so that "staging" get populated (and = we >>> are >>>>>>> the >>>>>>>>>> smart ones which will either launch a build for an update or = a >>> launch >>>>>>> for a >>>>>>>>>> complete rebuild) >>>>>>>>>> * commit the generated files in "staging" >>>>>>>>>> * "staging" get automatically deployed on >>>>>>>>>> http://incubator.staging.apache.org/easyant/ via svnpubsub >>>>>>>>>> * promoting to live will be about svn merging the "staging" = into >>> the >>>>>>>>>> "production" branch >>>>>>>>>> * the merge commit in "production" will be automatically be >>> deployed >>>>> on >>>>>>>>>> http://incubator.apache.org/easyant/ via svnpubsub >>>>>>>>>>=20 >>>>>>>>>> WDYT ? >>>>>>>>>>=20 >>>>>>>>>> Nicolas >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> -- >>>>>>>>> Jean Louis Boudart >>>>>>>>> Independent consultant >>>>>>>>> Project Lead http://www.easyant.org >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> -- >>>>>>>> Jean Louis Boudart >>>>>>>> Independent consultant >>>>>>>> Project Lead http://www.easyant.org >>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> -- >>>>>> Jean Louis Boudart >>>>>> Independent consultant >>>>>> Project Lead http://www.easyant.org >>>>>=20 >>>>>=20 >>>>=20 >>>>=20 >>>> -- >>>> Jean Louis Boudart >>>> Independent consultant >>>> Project Lead http://www.easyant.org >>>=20 >>>=20 >>=20 >>=20 >> -- >> Jean Louis Boudart >> Independent consultant >> Project Lead http://www.easyant.org >>=20 >=20 >=20 > --=20 > Jean Louis Boudart > Independent consultant > Project Lead http://www.easyant.org