You are viewing a plain text version of this content. The canonical link for it is here.
Posted to easyant-dev@incubator.apache.org by Jean-Louis Boudart <je...@gmail.com> on 2011/03/09 10:55:42 UTC
Re: Website
It seems that we can't have a staging website [1] except if we use Apache
CMS.
Now comes a few questions:
- 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" ?
2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> Looks good for me. I also think it would be great to have a staging
> website.
>
> 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 :
>
> - 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
>
> I created an issue for this (
> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
> there :p
>
>
>
> Le 28 février 2011 11:34, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
>
> Hi guys,
>>
>> (most of this email is quite a duplicate of the one I have done on
>> ant-dev)
>>
>> 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.
>>
>> 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.
>>
>> 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/.
>>
>> 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.
>>
>> 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
>>
>> WDYT ?
>>
>> Nicolas
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
Ooops i forgot the link
[1] https://issues.apache.org/jira/browse/INFRA-3488
2011/3/9 Jean-Louis Boudart <je...@gmail.com>
> It seems that we can't have a staging website [1] except if we use Apache
> CMS.
>
> Now comes a few questions:
>
> - 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" ?
>
>
>
> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>
> Looks good for me. I also think it would be great to have a staging
>> website.
>>
>> 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 :
>>
>> - 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
>>
>> I created an issue for this (
>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
>> there :p
>>
>>
>>
>> Le 28 février 2011 11:34, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit :
>>
>> Hi guys,
>>>
>>> (most of this email is quite a duplicate of the one I have done on
>>> ant-dev)
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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/.
>>>
>>> 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.
>>>
>>> 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
>>>
>>> WDYT ?
>>>
>>> Nicolas
>>>
>>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Project Lead http://www.easyant.org
>>
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
It's time to make Dr Myrmex live on our website / blog !
So let's make noise by asking people to help us to design it. Even if nobody
answers, at least it will bring attention on easyant.
<epic>
For the win !
</epic>
2011/3/23 Purkayastha, Siddhartha <Si...@ca.com>
> Hi All -
>
> For some context, EasyAnt reports all errors, diagnostic messages from 'Dr
> Myrmex'. For example, if a recommendation is to be made, the message we show
> says:
> 'Mr Myrmex recommends ...'
>
> For a new user to EasyAnt this may be a little confusing initially.
>
> I had a thought around having an image for Dr Myrmex, that we could have on
> all EasyAnt website / documentation / tutorials etc. This could be as though
> Mr Myrmex is communicating with the end users of EasyAnt. Perhaps, an ant in
> a white coat with specs and a stethoscope .. :-) However, I do not have much
> idea on how such an image could be created.
>
> On discussing with Jean Louis, he has made a suggestion, on which I would
> like to invite everyone's views:
> Publicise some kind of a contest for logo design contest in our blog. May
> be make some noise in twitter, ML etc.
> May be with the right kind of noise, we could get some help from outside,
> which we can acknowledge in our website / documentation etc.
>
> While I think it is an interesting idea, I am not sure of its feasibility.
>
> Suggestions welcome. Please also let us know if there is some other way
> that other Apache projects may have followed.
>
> Thanks,
> Siddhartha
>
> ________________________________
>
> From: Jean-Louis Boudart [mailto:jeanlouis.boudart@gmail.com]
> Sent: Wed 3/23/2011 2:59 AM
> To: easyant-dev@incubator.apache.org
> Subject: Re: Website
>
>
>
> Done !
>
> Here is the infra ticket :
> https://issues.apache.org/jira/browse/INFRA-3536
>
> 2011/3/22 Jean-Louis Boudart <je...@gmail.com>
>
> > I didn't get time to do it.
> > I plan to do it tonight if it's not already done.
> >
> > Le 18 mars 2011 17:34, Nicolas Lalevée <ni...@hibnet.org> a
> > écrit :
> >
> > I intended to do it myself but I was short on time. Hence no objection.
> >>
> >> Nicolas
> >>
> >> Le 18 mars 2011 à 16:51, Jean-Louis Boudart a écrit :
> >>
> >> > As there is no objections, could we open a ticket to INFRA to get it
> >> > published live ?
> >> >
> >> > Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a
> >> écrit
> >> > :
> >> >
> >> >>
> >> >> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
> >> >>
> >> >>> 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
> >> >>
> >> >>
> >> >>>
> >> >>> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
> >> >>>> Generated doc looks good for me !
> >> >>>>
> >> >>>> A few minor things to fix (it should not be blocking to go live) :
> >> >>>>
> >> >>>> - 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
> >> >>>>
> >> >>>>
> >> >>>> Le 14 mars 2011 15:41, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> >
> >> a
> >> >> écrit
> >> >>>> :
> >> >>>>
> >> >>>>> 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.
> >> >>>>>
> >> >>>>> I have then generated the site into the production branch:
> >> >>>>>
> https://svn.apache.org/repos/asf/incubator/easyant/site/production
> >> >>>>>
> >> >>>>> Please review the site before we get it live.
> >> >>>>>
> >> >>>>> Nicolas
> >> >>>>>
> >> >>>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
> >> >>>>>
> >> >>>>>> Done, the download page is also OK.
> >> >>>>>>
> >> >>>>>> After a quick review i think we could ask infrastructure team to
> >> put
> >> >> it
> >> >>>>> in
> >> >>>>>> place.
> >> >>>>>>
> >> >>>>>> What are missing ?
> >> >>>>>> Link to easyant documentation (svn:external pointing to
> >> >>>>>> src/documentation
> >> >>>>>> for example).
> >> >>>>>>
> >> >>>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org>
> >> a
> >> >>>>> écrit
> >> >>>>>> :
> >> >>>>>>
> >> >>>>>>> great work Jean-Louis.
> >> >>>>>>>
> >> >>>>>>> As an incubator project, Easyant website needs to follow the
> >> >> Incubator
> >> >>>>>>> branding:
> >> >>>>>>> http://incubator.apache.org/guides/branding.html
> >> >>>>>>>
> >> >>>>>>> So we nee to put a disclaimer in the home page and add the
> >> incubator
> >> >>>>> logo
> >> >>>>>>> in the header.
> >> >>>>>>>
> >> >>>>>>> Nicolas
> >> >>>>>>>
> >> >>>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
> >> >>>>>>>
> >> >>>>>>>> I've initialized a draft, we still need a download page linking
> >> old
> >> >>>>>>> release
> >> >>>>>>>> before Apache Incubator.
> >> >>>>>>>>
> >> >>>>>>>> Feedback are welcome
> >> >>>>>>>>
> >> >>>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <
> >> nicolas.lalevee@hibnet.org>
> >> >> a
> >> >>>>>>> écrit :
> >> >>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> >> >>>>>>>>>
> >> >>>>>>>>>> It seems that we can't have a staging website [1] except if
> we
> >> use
> >> >>>>>>> Apache
> >> >>>>>>>>>> CMS.
> >> >>>>>>>>>>
> >> >>>>>>>>>> Now comes a few questions:
> >> >>>>>>>>>>
> >> >>>>>>>>>> - 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" ?
> >> >>>>>>>>>
> >> >>>>>>>>> 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.
> >> >>>>>>>>>
> >> >>>>>>>>> Nicolas
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >> >>>>>>>>>>
> >> >>>>>>>>>>> Looks good for me. I also think it would be great to have a
> >> >>>>>>>>>>> staging
> >> >>>>>>>>>>> website.
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> 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 :
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> - 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
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> I created an issue for this (
> >> >>>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and
> >> attached a
> >> >>>>>>> draft
> >> >>>>>>>>>>> there :p
> >> >>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
> >> >>>>> nicolas.lalevee@hibnet.org
> >> >>>>>>>>
> >> >>>>>>>>> a
> >> >>>>>>>>>>> écrit :
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> Hi guys,
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> (most of this email is quite a duplicate of the one I have
> >> done
> >> >>>>>>>>>>>> on
> >> >>>>>>>>>>>> ant-dev)
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> 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.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> 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.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> 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/.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> 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.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> 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
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> WDYT ?
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> Nicolas
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> --
> >> >>>>>>>>>>> Jean Louis Boudart
> >> >>>>>>>>>>> Independent consultant
> >> >>>>>>>>>>> Project Lead http://www.easyant.org <
> http://www.easyant.org/>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>> --
> >> >>>>>>>>>> Jean Louis Boudart
> >> >>>>>>>>>> Independent consultant
> >> >>>>>>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/
> >
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>> --
> >> >>>>>>>> Jean Louis Boudart
> >> >>>>>>>> Independent consultant
> >> >>>>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> --
> >> >>>>>> Jean Louis Boudart
> >> >>>>>> Independent consultant
> >> >>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
> >> >>>>>
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Jean Louis Boudart
> >> >>>> Independent consultant
> >> >>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
> >> >>>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Jean Louis Boudart
> >> >>> Independent consultant
> >> >>> Project Lead http://www.easyant.org <http://www.easyant.org/>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Jean Louis Boudart
> >> > Independent consultant
> >> > Project Lead http://www.easyant.org <http://www.easyant.org/>
> >>
> >>
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org <http://www.easyant.org/>
> >
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org <http://www.easyant.org/>
>
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
RE: Website
Posted by "Purkayastha, Siddhartha" <Si...@ca.com>.
Hi All -
For some context, EasyAnt reports all errors, diagnostic messages from 'Dr Myrmex'. For example, if a recommendation is to be made, the message we show says:
'Mr Myrmex recommends ...'
For a new user to EasyAnt this may be a little confusing initially.
I had a thought around having an image for Dr Myrmex, that we could have on all EasyAnt website / documentation / tutorials etc. This could be as though Mr Myrmex is communicating with the end users of EasyAnt. Perhaps, an ant in a white coat with specs and a stethoscope .. :-) However, I do not have much idea on how such an image could be created.
On discussing with Jean Louis, he has made a suggestion, on which I would like to invite everyone's views:
Publicise some kind of a contest for logo design contest in our blog. May be make some noise in twitter, ML etc.
May be with the right kind of noise, we could get some help from outside, which we can acknowledge in our website / documentation etc.
While I think it is an interesting idea, I am not sure of its feasibility.
Suggestions welcome. Please also let us know if there is some other way that other Apache projects may have followed.
Thanks,
Siddhartha
________________________________
From: Jean-Louis Boudart [mailto:jeanlouis.boudart@gmail.com]
Sent: Wed 3/23/2011 2:59 AM
To: easyant-dev@incubator.apache.org
Subject: Re: Website
Done !
Here is the infra ticket : https://issues.apache.org/jira/browse/INFRA-3536
2011/3/22 Jean-Louis Boudart <je...@gmail.com>
> I didn't get time to do it.
> I plan to do it tonight if it's not already done.
>
> Le 18 mars 2011 17:34, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
>
> I intended to do it myself but I was short on time. Hence no objection.
>>
>> Nicolas
>>
>> Le 18 mars 2011 à 16:51, Jean-Louis Boudart a écrit :
>>
>> > As there is no objections, could we open a ticket to INFRA to get it
>> > published live ?
>> >
>> > Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit
>> > :
>> >
>> >>
>> >> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
>> >>
>> >>> 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
>> >>
>> >>
>> >>>
>> >>> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
>> >>>> Generated doc looks good for me !
>> >>>>
>> >>>> A few minor things to fix (it should not be blocking to go live) :
>> >>>>
>> >>>> - 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
>> >>>>
>> >>>>
>> >>>> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org>
>> a
>> >> écrit
>> >>>> :
>> >>>>
>> >>>>> 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.
>> >>>>>
>> >>>>> I have then generated the site into the production branch:
>> >>>>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>> >>>>>
>> >>>>> Please review the site before we get it live.
>> >>>>>
>> >>>>> Nicolas
>> >>>>>
>> >>>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>> >>>>>
>> >>>>>> Done, the download page is also OK.
>> >>>>>>
>> >>>>>> After a quick review i think we could ask infrastructure team to
>> put
>> >> it
>> >>>>> in
>> >>>>>> place.
>> >>>>>>
>> >>>>>> What are missing ?
>> >>>>>> Link to easyant documentation (svn:external pointing to
>> >>>>>> src/documentation
>> >>>>>> for example).
>> >>>>>>
>> >>>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org>
>> a
>> >>>>> écrit
>> >>>>>> :
>> >>>>>>
>> >>>>>>> great work Jean-Louis.
>> >>>>>>>
>> >>>>>>> As an incubator project, Easyant website needs to follow the
>> >> Incubator
>> >>>>>>> branding:
>> >>>>>>> http://incubator.apache.org/guides/branding.html
>> >>>>>>>
>> >>>>>>> So we nee to put a disclaimer in the home page and add the
>> incubator
>> >>>>> logo
>> >>>>>>> in the header.
>> >>>>>>>
>> >>>>>>> Nicolas
>> >>>>>>>
>> >>>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>> >>>>>>>
>> >>>>>>>> I've initialized a draft, we still need a download page linking
>> old
>> >>>>>>> release
>> >>>>>>>> before Apache Incubator.
>> >>>>>>>>
>> >>>>>>>> Feedback are welcome
>> >>>>>>>>
>> >>>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org>
>> >> a
>> >>>>>>> écrit :
>> >>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>> >>>>>>>>>
>> >>>>>>>>>> It seems that we can't have a staging website [1] except if we
>> use
>> >>>>>>> Apache
>> >>>>>>>>>> CMS.
>> >>>>>>>>>>
>> >>>>>>>>>> Now comes a few questions:
>> >>>>>>>>>>
>> >>>>>>>>>> - 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" ?
>> >>>>>>>>>
>> >>>>>>>>> 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.
>> >>>>>>>>>
>> >>>>>>>>> Nicolas
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>> >>>>>>>>>>
>> >>>>>>>>>>> Looks good for me. I also think it would be great to have a
>> >>>>>>>>>>> staging
>> >>>>>>>>>>> website.
>> >>>>>>>>>>>
>> >>>>>>>>>>> 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 :
>> >>>>>>>>>>>
>> >>>>>>>>>>> - 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
>> >>>>>>>>>>>
>> >>>>>>>>>>> I created an issue for this (
>> >>>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and
>> attached a
>> >>>>>>> draft
>> >>>>>>>>>>> there :p
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
>> >>>>> nicolas.lalevee@hibnet.org
>> >>>>>>>>
>> >>>>>>>>> a
>> >>>>>>>>>>> écrit :
>> >>>>>>>>>>>
>> >>>>>>>>>>> Hi guys,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> (most of this email is quite a duplicate of the one I have
>> done
>> >>>>>>>>>>>> on
>> >>>>>>>>>>>> ant-dev)
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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/.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> WDYT ?
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Nicolas
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> --
>> >>>>>>>>>>> Jean Louis Boudart
>> >>>>>>>>>>> Independent consultant
>> >>>>>>>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Jean Louis Boudart
>> >>>>>>>>>> Independent consultant
>> >>>>>>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Jean Louis Boudart
>> >>>>>>>> Independent consultant
>> >>>>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Jean Louis Boudart
>> >>>>>> Independent consultant
>> >>>>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Jean Louis Boudart
>> >>>> Independent consultant
>> >>>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Jean Louis Boudart
>> >>> Independent consultant
>> >>> Project Lead http://www.easyant.org <http://www.easyant.org/>
>> >>
>> >>
>> >
>> >
>> > --
>> > Jean Louis Boudart
>> > Independent consultant
>> > Project Lead http://www.easyant.org <http://www.easyant.org/>
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org <http://www.easyant.org/>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org <http://www.easyant.org/>
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
Done !
Here is the infra ticket : https://issues.apache.org/jira/browse/INFRA-3536
2011/3/22 Jean-Louis Boudart <je...@gmail.com>
> I didn't get time to do it.
> I plan to do it tonight if it's not already done.
>
> Le 18 mars 2011 17:34, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
>
> I intended to do it myself but I was short on time. Hence no objection.
>>
>> Nicolas
>>
>> Le 18 mars 2011 à 16:51, Jean-Louis Boudart a écrit :
>>
>> > As there is no objections, could we open a ticket to INFRA to get it
>> > published live ?
>> >
>> > Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit
>> > :
>> >
>> >>
>> >> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
>> >>
>> >>> 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
>> >>
>> >>
>> >>>
>> >>> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
>> >>>> Generated doc looks good for me !
>> >>>>
>> >>>> A few minor things to fix (it should not be blocking to go live) :
>> >>>>
>> >>>> - 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
>> >>>>
>> >>>>
>> >>>> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org>
>> a
>> >> écrit
>> >>>> :
>> >>>>
>> >>>>> 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.
>> >>>>>
>> >>>>> I have then generated the site into the production branch:
>> >>>>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>> >>>>>
>> >>>>> Please review the site before we get it live.
>> >>>>>
>> >>>>> Nicolas
>> >>>>>
>> >>>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>> >>>>>
>> >>>>>> Done, the download page is also OK.
>> >>>>>>
>> >>>>>> After a quick review i think we could ask infrastructure team to
>> put
>> >> it
>> >>>>> in
>> >>>>>> place.
>> >>>>>>
>> >>>>>> What are missing ?
>> >>>>>> Link to easyant documentation (svn:external pointing to
>> >>>>>> src/documentation
>> >>>>>> for example).
>> >>>>>>
>> >>>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org>
>> a
>> >>>>> écrit
>> >>>>>> :
>> >>>>>>
>> >>>>>>> great work Jean-Louis.
>> >>>>>>>
>> >>>>>>> As an incubator project, Easyant website needs to follow the
>> >> Incubator
>> >>>>>>> branding:
>> >>>>>>> http://incubator.apache.org/guides/branding.html
>> >>>>>>>
>> >>>>>>> So we nee to put a disclaimer in the home page and add the
>> incubator
>> >>>>> logo
>> >>>>>>> in the header.
>> >>>>>>>
>> >>>>>>> Nicolas
>> >>>>>>>
>> >>>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>> >>>>>>>
>> >>>>>>>> I've initialized a draft, we still need a download page linking
>> old
>> >>>>>>> release
>> >>>>>>>> before Apache Incubator.
>> >>>>>>>>
>> >>>>>>>> Feedback are welcome
>> >>>>>>>>
>> >>>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org>
>> >> a
>> >>>>>>> écrit :
>> >>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>> >>>>>>>>>
>> >>>>>>>>>> It seems that we can't have a staging website [1] except if we
>> use
>> >>>>>>> Apache
>> >>>>>>>>>> CMS.
>> >>>>>>>>>>
>> >>>>>>>>>> Now comes a few questions:
>> >>>>>>>>>>
>> >>>>>>>>>> - 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" ?
>> >>>>>>>>>
>> >>>>>>>>> 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.
>> >>>>>>>>>
>> >>>>>>>>> Nicolas
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>> >>>>>>>>>>
>> >>>>>>>>>>> Looks good for me. I also think it would be great to have a
>> >>>>>>>>>>> staging
>> >>>>>>>>>>> website.
>> >>>>>>>>>>>
>> >>>>>>>>>>> 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 :
>> >>>>>>>>>>>
>> >>>>>>>>>>> - 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
>> >>>>>>>>>>>
>> >>>>>>>>>>> I created an issue for this (
>> >>>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and
>> attached a
>> >>>>>>> draft
>> >>>>>>>>>>> there :p
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
>> >>>>> nicolas.lalevee@hibnet.org
>> >>>>>>>>
>> >>>>>>>>> a
>> >>>>>>>>>>> écrit :
>> >>>>>>>>>>>
>> >>>>>>>>>>> Hi guys,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> (most of this email is quite a duplicate of the one I have
>> done
>> >>>>>>>>>>>> on
>> >>>>>>>>>>>> ant-dev)
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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/.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 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
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> WDYT ?
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Nicolas
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> --
>> >>>>>>>>>>> Jean Louis Boudart
>> >>>>>>>>>>> Independent consultant
>> >>>>>>>>>>> Project Lead http://www.easyant.org
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Jean Louis Boudart
>> >>>>>>>>>> Independent consultant
>> >>>>>>>>>> Project Lead http://www.easyant.org
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Jean Louis Boudart
>> >>>>>>>> Independent consultant
>> >>>>>>>> Project Lead http://www.easyant.org
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Jean Louis Boudart
>> >>>>>> Independent consultant
>> >>>>>> Project Lead http://www.easyant.org
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Jean Louis Boudart
>> >>>> Independent consultant
>> >>>> Project Lead http://www.easyant.org
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Jean Louis Boudart
>> >>> Independent consultant
>> >>> Project Lead http://www.easyant.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Jean Louis Boudart
>> > Independent consultant
>> > Project Lead http://www.easyant.org
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
I didn't get time to do it.
I plan to do it tonight if it's not already done.
Le 18 mars 2011 17:34, Nicolas Lalevée <ni...@hibnet.org> a écrit
:
> I intended to do it myself but I was short on time. Hence no objection.
>
> Nicolas
>
> Le 18 mars 2011 à 16:51, Jean-Louis Boudart a écrit :
>
> > As there is no objections, could we open a ticket to INFRA to get it
> > published live ?
> >
> > Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a
> écrit
> > :
> >
> >>
> >> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
> >>
> >>> 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
> >>
> >>
> >>>
> >>> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
> >>>> Generated doc looks good for me !
> >>>>
> >>>> A few minor things to fix (it should not be blocking to go live) :
> >>>>
> >>>> - 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
> >>>>
> >>>>
> >>>> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a
> >> écrit
> >>>> :
> >>>>
> >>>>> 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.
> >>>>>
> >>>>> I have then generated the site into the production branch:
> >>>>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
> >>>>>
> >>>>> Please review the site before we get it live.
> >>>>>
> >>>>> Nicolas
> >>>>>
> >>>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
> >>>>>
> >>>>>> Done, the download page is also OK.
> >>>>>>
> >>>>>> After a quick review i think we could ask infrastructure team to put
> >> it
> >>>>> in
> >>>>>> place.
> >>>>>>
> >>>>>> What are missing ?
> >>>>>> Link to easyant documentation (svn:external pointing to
> >>>>>> src/documentation
> >>>>>> for example).
> >>>>>>
> >>>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org>
> a
> >>>>> écrit
> >>>>>> :
> >>>>>>
> >>>>>>> great work Jean-Louis.
> >>>>>>>
> >>>>>>> As an incubator project, Easyant website needs to follow the
> >> Incubator
> >>>>>>> branding:
> >>>>>>> http://incubator.apache.org/guides/branding.html
> >>>>>>>
> >>>>>>> So we nee to put a disclaimer in the home page and add the
> incubator
> >>>>> logo
> >>>>>>> in the header.
> >>>>>>>
> >>>>>>> Nicolas
> >>>>>>>
> >>>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
> >>>>>>>
> >>>>>>>> I've initialized a draft, we still need a download page linking
> old
> >>>>>>> release
> >>>>>>>> before Apache Incubator.
> >>>>>>>>
> >>>>>>>> Feedback are welcome
> >>>>>>>>
> >>>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> >
> >> a
> >>>>>>> écrit :
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> >>>>>>>>>
> >>>>>>>>>> It seems that we can't have a staging website [1] except if we
> use
> >>>>>>> Apache
> >>>>>>>>>> CMS.
> >>>>>>>>>>
> >>>>>>>>>> Now comes a few questions:
> >>>>>>>>>>
> >>>>>>>>>> - 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" ?
> >>>>>>>>>
> >>>>>>>>> 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.
> >>>>>>>>>
> >>>>>>>>> Nicolas
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >>>>>>>>>>
> >>>>>>>>>>> Looks good for me. I also think it would be great to have a
> >>>>>>>>>>> staging
> >>>>>>>>>>> website.
> >>>>>>>>>>>
> >>>>>>>>>>> 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 :
> >>>>>>>>>>>
> >>>>>>>>>>> - 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
> >>>>>>>>>>>
> >>>>>>>>>>> I created an issue for this (
> >>>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached
> a
> >>>>>>> draft
> >>>>>>>>>>> there :p
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
> >>>>> nicolas.lalevee@hibnet.org
> >>>>>>>>
> >>>>>>>>> a
> >>>>>>>>>>> écrit :
> >>>>>>>>>>>
> >>>>>>>>>>> Hi guys,
> >>>>>>>>>>>>
> >>>>>>>>>>>> (most of this email is quite a duplicate of the one I have
> done
> >>>>>>>>>>>> on
> >>>>>>>>>>>> ant-dev)
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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
> .
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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.
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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/.
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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.
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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
> >>>>>>>>>>>>
> >>>>>>>>>>>> WDYT ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Nicolas
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Jean Louis Boudart
> >>>>>>>>>>> Independent consultant
> >>>>>>>>>>> Project Lead http://www.easyant.org
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Jean Louis Boudart
> >>>>>>>>>> Independent consultant
> >>>>>>>>>> Project Lead http://www.easyant.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Jean Louis Boudart
> >>>>>>>> Independent consultant
> >>>>>>>> Project Lead http://www.easyant.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Jean Louis Boudart
> >>>>>> Independent consultant
> >>>>>> Project Lead http://www.easyant.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Jean Louis Boudart
> >>>> Independent consultant
> >>>> Project Lead http://www.easyant.org
> >>>>
> >>>
> >>>
> >>> --
> >>> Jean Louis Boudart
> >>> Independent consultant
> >>> Project Lead http://www.easyant.org
> >>
> >>
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I intended to do it myself but I was short on time. Hence no objection.
Nicolas
Le 18 mars 2011 à 16:51, Jean-Louis Boudart a écrit :
> As there is no objections, could we open a ticket to INFRA to get it
> published live ?
>
> Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a écrit
> :
>
>>
>> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
>>
>>> 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
>>
>>
>>>
>>> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
>>>> Generated doc looks good for me !
>>>>
>>>> A few minor things to fix (it should not be blocking to go live) :
>>>>
>>>> - 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
>>>>
>>>>
>>>> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit
>>>> :
>>>>
>>>>> 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.
>>>>>
>>>>> I have then generated the site into the production branch:
>>>>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>>>>>
>>>>> Please review the site before we get it live.
>>>>>
>>>>> Nicolas
>>>>>
>>>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>>>>>
>>>>>> Done, the download page is also OK.
>>>>>>
>>>>>> After a quick review i think we could ask infrastructure team to put
>> it
>>>>> in
>>>>>> place.
>>>>>>
>>>>>> What are missing ?
>>>>>> Link to easyant documentation (svn:external pointing to
>>>>>> src/documentation
>>>>>> for example).
>>>>>>
>>>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a
>>>>> écrit
>>>>>> :
>>>>>>
>>>>>>> great work Jean-Louis.
>>>>>>>
>>>>>>> As an incubator project, Easyant website needs to follow the
>> Incubator
>>>>>>> branding:
>>>>>>> http://incubator.apache.org/guides/branding.html
>>>>>>>
>>>>>>> So we nee to put a disclaimer in the home page and add the incubator
>>>>> logo
>>>>>>> in the header.
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>>>>>>>
>>>>>>>> I've initialized a draft, we still need a download page linking old
>>>>>>> release
>>>>>>>> before Apache Incubator.
>>>>>>>>
>>>>>>>> Feedback are welcome
>>>>>>>>
>>>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org>
>> a
>>>>>>> écrit :
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>>>>>>>>>
>>>>>>>>>> It seems that we can't have a staging website [1] except if we use
>>>>>>> Apache
>>>>>>>>>> CMS.
>>>>>>>>>>
>>>>>>>>>> Now comes a few questions:
>>>>>>>>>>
>>>>>>>>>> - 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" ?
>>>>>>>>>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>> Nicolas
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>>>>>>>>>>
>>>>>>>>>>> Looks good for me. I also think it would be great to have a
>>>>>>>>>>> staging
>>>>>>>>>>> website.
>>>>>>>>>>>
>>>>>>>>>>> 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 :
>>>>>>>>>>>
>>>>>>>>>>> - 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
>>>>>>>>>>>
>>>>>>>>>>> I created an issue for this (
>>>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
>>>>>>> draft
>>>>>>>>>>> there :p
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
>>>>> nicolas.lalevee@hibnet.org
>>>>>>>>
>>>>>>>>> a
>>>>>>>>>>> écrit :
>>>>>>>>>>>
>>>>>>>>>>> Hi guys,
>>>>>>>>>>>>
>>>>>>>>>>>> (most of this email is quite a duplicate of the one I have done
>>>>>>>>>>>> on
>>>>>>>>>>>> ant-dev)
>>>>>>>>>>>>
>>>>>>>>>>>> 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.
>>>>>>>>>>>>
>>>>>>>>>>>> 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.
>>>>>>>>>>>>
>>>>>>>>>>>> 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/.
>>>>>>>>>>>>
>>>>>>>>>>>> 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.
>>>>>>>>>>>>
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>> WDYT ?
>>>>>>>>>>>>
>>>>>>>>>>>> Nicolas
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Jean Louis Boudart
>>>>>>>>>>> Independent consultant
>>>>>>>>>>> Project Lead http://www.easyant.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jean Louis Boudart
>>>>>>>>>> Independent consultant
>>>>>>>>>> Project Lead http://www.easyant.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean Louis Boudart
>>>>>>>> Independent consultant
>>>>>>>> Project Lead http://www.easyant.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean Louis Boudart
>>>>>> Independent consultant
>>>>>> Project Lead http://www.easyant.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jean Louis Boudart
>>>> Independent consultant
>>>> Project Lead http://www.easyant.org
>>>>
>>>
>>>
>>> --
>>> Jean Louis Boudart
>>> Independent consultant
>>> Project Lead http://www.easyant.org
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
As there is no objections, could we open a ticket to INFRA to get it
published live ?
Le 15 mars 2011 10:09, Nicolas Lalevée <ni...@hibnet.org> a écrit
:
>
> Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
>
> > 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
>
>
> >
> > 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
> >> Generated doc looks good for me !
> >>
> >> A few minor things to fix (it should not be blocking to go live) :
> >>
> >> - 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
> >>
> >>
> >> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a
> écrit
> >> :
> >>
> >>> 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.
> >>>
> >>> I have then generated the site into the production branch:
> >>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
> >>>
> >>> Please review the site before we get it live.
> >>>
> >>> Nicolas
> >>>
> >>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
> >>>
> >>>> Done, the download page is also OK.
> >>>>
> >>>> After a quick review i think we could ask infrastructure team to put
> it
> >>> in
> >>>> place.
> >>>>
> >>>> What are missing ?
> >>>> Link to easyant documentation (svn:external pointing to
> >>>> src/documentation
> >>>> for example).
> >>>>
> >>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a
> >>> écrit
> >>>> :
> >>>>
> >>>>> great work Jean-Louis.
> >>>>>
> >>>>> As an incubator project, Easyant website needs to follow the
> Incubator
> >>>>> branding:
> >>>>> http://incubator.apache.org/guides/branding.html
> >>>>>
> >>>>> So we nee to put a disclaimer in the home page and add the incubator
> >>> logo
> >>>>> in the header.
> >>>>>
> >>>>> Nicolas
> >>>>>
> >>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
> >>>>>
> >>>>>> I've initialized a draft, we still need a download page linking old
> >>>>> release
> >>>>>> before Apache Incubator.
> >>>>>>
> >>>>>> Feedback are welcome
> >>>>>>
> >>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org>
> a
> >>>>> écrit :
> >>>>>>
> >>>>>>>
> >>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> >>>>>>>
> >>>>>>>> It seems that we can't have a staging website [1] except if we use
> >>>>> Apache
> >>>>>>>> CMS.
> >>>>>>>>
> >>>>>>>> Now comes a few questions:
> >>>>>>>>
> >>>>>>>> - 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" ?
> >>>>>>>
> >>>>>>> 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.
> >>>>>>>
> >>>>>>> Nicolas
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >>>>>>>>
> >>>>>>>>> Looks good for me. I also think it would be great to have a
> >>>>>>>>> staging
> >>>>>>>>> website.
> >>>>>>>>>
> >>>>>>>>> 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 :
> >>>>>>>>>
> >>>>>>>>> - 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
> >>>>>>>>>
> >>>>>>>>> I created an issue for this (
> >>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
> >>>>> draft
> >>>>>>>>> there :p
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
> >>> nicolas.lalevee@hibnet.org
> >>>>>>
> >>>>>>> a
> >>>>>>>>> écrit :
> >>>>>>>>>
> >>>>>>>>> Hi guys,
> >>>>>>>>>>
> >>>>>>>>>> (most of this email is quite a duplicate of the one I have done
> >>>>>>>>>> on
> >>>>>>>>>> ant-dev)
> >>>>>>>>>>
> >>>>>>>>>> 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.
> >>>>>>>>>>
> >>>>>>>>>> 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.
> >>>>>>>>>>
> >>>>>>>>>> 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/.
> >>>>>>>>>>
> >>>>>>>>>> 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.
> >>>>>>>>>>
> >>>>>>>>>> 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
> >>>>>>>>>>
> >>>>>>>>>> WDYT ?
> >>>>>>>>>>
> >>>>>>>>>> Nicolas
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Jean Louis Boudart
> >>>>>>>>> Independent consultant
> >>>>>>>>> Project Lead http://www.easyant.org
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Jean Louis Boudart
> >>>>>>>> Independent consultant
> >>>>>>>> Project Lead http://www.easyant.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Jean Louis Boudart
> >>>>>> Independent consultant
> >>>>>> Project Lead http://www.easyant.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Jean Louis Boudart
> >>>> Independent consultant
> >>>> Project Lead http://www.easyant.org
> >>>
> >>>
> >>
> >>
> >> --
> >> Jean Louis Boudart
> >> Independent consultant
> >> Project Lead http://www.easyant.org
> >>
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 15 mars 2011 à 09:01, Jean-Louis Boudart a écrit :
> 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
>
> 2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
>> Generated doc looks good for me !
>>
>> A few minor things to fix (it should not be blocking to go live) :
>>
>> - 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
>>
>>
>> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a écrit
>> :
>>
>>> 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.
>>>
>>> I have then generated the site into the production branch:
>>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>>>
>>> Please review the site before we get it live.
>>>
>>> Nicolas
>>>
>>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>>>
>>>> Done, the download page is also OK.
>>>>
>>>> After a quick review i think we could ask infrastructure team to put it
>>> in
>>>> place.
>>>>
>>>> What are missing ?
>>>> Link to easyant documentation (svn:external pointing to
>>>> src/documentation
>>>> for example).
>>>>
>>>> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a
>>> écrit
>>>> :
>>>>
>>>>> great work Jean-Louis.
>>>>>
>>>>> As an incubator project, Easyant website needs to follow the Incubator
>>>>> branding:
>>>>> http://incubator.apache.org/guides/branding.html
>>>>>
>>>>> So we nee to put a disclaimer in the home page and add the incubator
>>> logo
>>>>> in the header.
>>>>>
>>>>> Nicolas
>>>>>
>>>>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>>>>>
>>>>>> I've initialized a draft, we still need a download page linking old
>>>>> release
>>>>>> before Apache Incubator.
>>>>>>
>>>>>> Feedback are welcome
>>>>>>
>>>>>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a
>>>>> écrit :
>>>>>>
>>>>>>>
>>>>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>>>>>>>
>>>>>>>> It seems that we can't have a staging website [1] except if we use
>>>>> Apache
>>>>>>>> CMS.
>>>>>>>>
>>>>>>>> Now comes a few questions:
>>>>>>>>
>>>>>>>> - 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" ?
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>>>>>>>>
>>>>>>>>> Looks good for me. I also think it would be great to have a
>>>>>>>>> staging
>>>>>>>>> website.
>>>>>>>>>
>>>>>>>>> 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 :
>>>>>>>>>
>>>>>>>>> - 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
>>>>>>>>>
>>>>>>>>> I created an issue for this (
>>>>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
>>>>> draft
>>>>>>>>> there :p
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
>>> nicolas.lalevee@hibnet.org
>>>>>>
>>>>>>> a
>>>>>>>>> écrit :
>>>>>>>>>
>>>>>>>>> Hi guys,
>>>>>>>>>>
>>>>>>>>>> (most of this email is quite a duplicate of the one I have done
>>>>>>>>>> on
>>>>>>>>>> ant-dev)
>>>>>>>>>>
>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>>> 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/.
>>>>>>>>>>
>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>> WDYT ?
>>>>>>>>>>
>>>>>>>>>> Nicolas
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jean Louis Boudart
>>>>>>>>> Independent consultant
>>>>>>>>> Project Lead http://www.easyant.org
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean Louis Boudart
>>>>>>>> Independent consultant
>>>>>>>> Project Lead http://www.easyant.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean Louis Boudart
>>>>>> Independent consultant
>>>>>> Project Lead http://www.easyant.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jean Louis Boudart
>>>> Independent consultant
>>>> Project Lead http://www.easyant.org
>>>
>>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Project Lead http://www.easyant.org
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
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 ?)
2011/3/14, Jean-Louis Boudart <je...@gmail.com>:
> Generated doc looks good for me !
>
> A few minor things to fix (it should not be blocking to go live) :
>
> - 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
>
>
> Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a écrit
> :
>
>> 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.
>>
>> I have then generated the site into the production branch:
>> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>>
>> Please review the site before we get it live.
>>
>> Nicolas
>>
>> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>>
>> > Done, the download page is also OK.
>> >
>> > After a quick review i think we could ask infrastructure team to put it
>> in
>> > place.
>> >
>> > What are missing ?
>> > Link to easyant documentation (svn:external pointing to
>> > src/documentation
>> > for example).
>> >
>> > Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit
>> > :
>> >
>> >> great work Jean-Louis.
>> >>
>> >> As an incubator project, Easyant website needs to follow the Incubator
>> >> branding:
>> >> http://incubator.apache.org/guides/branding.html
>> >>
>> >> So we nee to put a disclaimer in the home page and add the incubator
>> logo
>> >> in the header.
>> >>
>> >> Nicolas
>> >>
>> >> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>> >>
>> >>> I've initialized a draft, we still need a download page linking old
>> >> release
>> >>> before Apache Incubator.
>> >>>
>> >>> Feedback are welcome
>> >>>
>> >>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a
>> >> écrit :
>> >>>
>> >>>>
>> >>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>> >>>>
>> >>>>> It seems that we can't have a staging website [1] except if we use
>> >> Apache
>> >>>>> CMS.
>> >>>>>
>> >>>>> Now comes a few questions:
>> >>>>>
>> >>>>> - 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" ?
>> >>>>
>> >>>> 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.
>> >>>>
>> >>>> Nicolas
>> >>>>
>> >>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>> >>>>>
>> >>>>>> Looks good for me. I also think it would be great to have a
>> >>>>>> staging
>> >>>>>> website.
>> >>>>>>
>> >>>>>> 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 :
>> >>>>>>
>> >>>>>> - 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
>> >>>>>>
>> >>>>>> I created an issue for this (
>> >>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
>> >> draft
>> >>>>>> there :p
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org
>> >>>
>> >>>> a
>> >>>>>> écrit :
>> >>>>>>
>> >>>>>> Hi guys,
>> >>>>>>>
>> >>>>>>> (most of this email is quite a duplicate of the one I have done
>> >>>>>>> on
>> >>>>>>> ant-dev)
>> >>>>>>>
>> >>>>>>> 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.
>> >>>>>>>
>> >>>>>>> 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.
>> >>>>>>>
>> >>>>>>> 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/.
>> >>>>>>>
>> >>>>>>> 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.
>> >>>>>>>
>> >>>>>>> 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
>> >>>>>>>
>> >>>>>>> WDYT ?
>> >>>>>>>
>> >>>>>>> Nicolas
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Jean Louis Boudart
>> >>>>>> Independent consultant
>> >>>>>> Project Lead http://www.easyant.org
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Jean Louis Boudart
>> >>>>> Independent consultant
>> >>>>> Project Lead http://www.easyant.org
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Jean Louis Boudart
>> >>> Independent consultant
>> >>> Project Lead http://www.easyant.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Jean Louis Boudart
>> > Independent consultant
>> > Project Lead http://www.easyant.org
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
Generated doc looks good for me !
A few minor things to fix (it should not be blocking to go live) :
- 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
Le 14 mars 2011 15:41, Nicolas Lalevée <ni...@hibnet.org> a écrit
:
> 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.
>
> I have then generated the site into the production branch:
> https://svn.apache.org/repos/asf/incubator/easyant/site/production
>
> Please review the site before we get it live.
>
> Nicolas
>
> Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
>
> > Done, the download page is also OK.
> >
> > After a quick review i think we could ask infrastructure team to put it
> in
> > place.
> >
> > What are missing ?
> > Link to easyant documentation (svn:external pointing to src/documentation
> > for example).
> >
> > Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a
> écrit
> > :
> >
> >> great work Jean-Louis.
> >>
> >> As an incubator project, Easyant website needs to follow the Incubator
> >> branding:
> >> http://incubator.apache.org/guides/branding.html
> >>
> >> So we nee to put a disclaimer in the home page and add the incubator
> logo
> >> in the header.
> >>
> >> Nicolas
> >>
> >> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
> >>
> >>> I've initialized a draft, we still need a download page linking old
> >> release
> >>> before Apache Incubator.
> >>>
> >>> Feedback are welcome
> >>>
> >>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a
> >> écrit :
> >>>
> >>>>
> >>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> >>>>
> >>>>> It seems that we can't have a staging website [1] except if we use
> >> Apache
> >>>>> CMS.
> >>>>>
> >>>>> Now comes a few questions:
> >>>>>
> >>>>> - 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" ?
> >>>>
> >>>> 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.
> >>>>
> >>>> Nicolas
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >>>>>
> >>>>>> Looks good for me. I also think it would be great to have a staging
> >>>>>> website.
> >>>>>>
> >>>>>> 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 :
> >>>>>>
> >>>>>> - 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
> >>>>>>
> >>>>>> I created an issue for this (
> >>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
> >> draft
> >>>>>> there :p
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org
> >>>
> >>>> a
> >>>>>> écrit :
> >>>>>>
> >>>>>> Hi guys,
> >>>>>>>
> >>>>>>> (most of this email is quite a duplicate of the one I have done on
> >>>>>>> ant-dev)
> >>>>>>>
> >>>>>>> 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.
> >>>>>>>
> >>>>>>> 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.
> >>>>>>>
> >>>>>>> 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/.
> >>>>>>>
> >>>>>>> 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.
> >>>>>>>
> >>>>>>> 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
> >>>>>>>
> >>>>>>> WDYT ?
> >>>>>>>
> >>>>>>> Nicolas
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Jean Louis Boudart
> >>>>>> Independent consultant
> >>>>>> Project Lead http://www.easyant.org
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Jean Louis Boudart
> >>>>> Independent consultant
> >>>>> Project Lead http://www.easyant.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Jean Louis Boudart
> >>> Independent consultant
> >>> Project Lead http://www.easyant.org
> >>
> >>
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Nicolas Lalevée <ni...@hibnet.org>.
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.
I have then generated the site into the production branch:
https://svn.apache.org/repos/asf/incubator/easyant/site/production
Please review the site before we get it live.
Nicolas
Le 13 mars 2011 à 18:39, Jean-Louis Boudart a écrit :
> Done, the download page is also OK.
>
> After a quick review i think we could ask infrastructure team to put it in
> place.
>
> What are missing ?
> Link to easyant documentation (svn:external pointing to src/documentation
> for example).
>
> Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a écrit
> :
>
>> great work Jean-Louis.
>>
>> As an incubator project, Easyant website needs to follow the Incubator
>> branding:
>> http://incubator.apache.org/guides/branding.html
>>
>> So we nee to put a disclaimer in the home page and add the incubator logo
>> in the header.
>>
>> Nicolas
>>
>> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>>
>>> I've initialized a draft, we still need a download page linking old
>> release
>>> before Apache Incubator.
>>>
>>> Feedback are welcome
>>>
>>> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit :
>>>
>>>>
>>>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>>>>
>>>>> It seems that we can't have a staging website [1] except if we use
>> Apache
>>>>> CMS.
>>>>>
>>>>> Now comes a few questions:
>>>>>
>>>>> - 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" ?
>>>>
>>>> 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.
>>>>
>>>> Nicolas
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>>>>>
>>>>>> Looks good for me. I also think it would be great to have a staging
>>>>>> website.
>>>>>>
>>>>>> 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 :
>>>>>>
>>>>>> - 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
>>>>>>
>>>>>> I created an issue for this (
>>>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
>> draft
>>>>>> there :p
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le 28 février 2011 11:34, Nicolas Lalevée <nicolas.lalevee@hibnet.org
>>>
>>>> a
>>>>>> écrit :
>>>>>>
>>>>>> Hi guys,
>>>>>>>
>>>>>>> (most of this email is quite a duplicate of the one I have done on
>>>>>>> ant-dev)
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> 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/.
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>> WDYT ?
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean Louis Boudart
>>>>>> Independent consultant
>>>>>> Project Lead http://www.easyant.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jean Louis Boudart
>>>>> Independent consultant
>>>>> Project Lead http://www.easyant.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Jean Louis Boudart
>>> Independent consultant
>>> Project Lead http://www.easyant.org
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
Done, the download page is also OK.
After a quick review i think we could ask infrastructure team to put it in
place.
What are missing ?
Link to easyant documentation (svn:external pointing to src/documentation
for example).
Le 11 mars 2011 16:23, Nicolas Lalevée <ni...@hibnet.org> a écrit
:
> great work Jean-Louis.
>
> As an incubator project, Easyant website needs to follow the Incubator
> branding:
> http://incubator.apache.org/guides/branding.html
>
> So we nee to put a disclaimer in the home page and add the incubator logo
> in the header.
>
> Nicolas
>
> Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
>
> > I've initialized a draft, we still need a download page linking old
> release
> > before Apache Incubator.
> >
> > Feedback are welcome
> >
> > Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
> >
> >>
> >> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> >>
> >>> It seems that we can't have a staging website [1] except if we use
> Apache
> >>> CMS.
> >>>
> >>> Now comes a few questions:
> >>>
> >>> - 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" ?
> >>
> >> 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.
> >>
> >> Nicolas
> >>
> >>
> >>>
> >>>
> >>>
> >>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >>>
> >>>> Looks good for me. I also think it would be great to have a staging
> >>>> website.
> >>>>
> >>>> 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 :
> >>>>
> >>>> - 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
> >>>>
> >>>> I created an issue for this (
> >>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a
> draft
> >>>> there :p
> >>>>
> >>>>
> >>>>
> >>>> Le 28 février 2011 11:34, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> >
> >> a
> >>>> écrit :
> >>>>
> >>>> Hi guys,
> >>>>>
> >>>>> (most of this email is quite a duplicate of the one I have done on
> >>>>> ant-dev)
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>> 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/.
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>> 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
> >>>>>
> >>>>> WDYT ?
> >>>>>
> >>>>> Nicolas
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Jean Louis Boudart
> >>>> Independent consultant
> >>>> Project Lead http://www.easyant.org
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Jean Louis Boudart
> >>> Independent consultant
> >>> Project Lead http://www.easyant.org
> >>
> >>
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Nicolas Lalevée <ni...@hibnet.org>.
great work Jean-Louis.
As an incubator project, Easyant website needs to follow the Incubator branding:
http://incubator.apache.org/guides/branding.html
So we nee to put a disclaimer in the home page and add the incubator logo in the header.
Nicolas
Le 11 mars 2011 à 16:07, Jean-Louis Boudart a écrit :
> I've initialized a draft, we still need a download page linking old release
> before Apache Incubator.
>
> Feedback are welcome
>
> Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a écrit :
>
>>
>> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>>
>>> It seems that we can't have a staging website [1] except if we use Apache
>>> CMS.
>>>
>>> Now comes a few questions:
>>>
>>> - 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" ?
>>
>> 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.
>>
>> Nicolas
>>
>>
>>>
>>>
>>>
>>> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>>>
>>>> Looks good for me. I also think it would be great to have a staging
>>>> website.
>>>>
>>>> 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 :
>>>>
>>>> - 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
>>>>
>>>> I created an issue for this (
>>>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
>>>> there :p
>>>>
>>>>
>>>>
>>>> Le 28 février 2011 11:34, Nicolas Lalevée <ni...@hibnet.org>
>> a
>>>> écrit :
>>>>
>>>> Hi guys,
>>>>>
>>>>> (most of this email is quite a duplicate of the one I have done on
>>>>> ant-dev)
>>>>>
>>>>> 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.
>>>>>
>>>>> 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.
>>>>>
>>>>> 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/.
>>>>>
>>>>> 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.
>>>>>
>>>>> 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
>>>>>
>>>>> WDYT ?
>>>>>
>>>>> Nicolas
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jean Louis Boudart
>>>> Independent consultant
>>>> Project Lead http://www.easyant.org
>>>>
>>>
>>>
>>>
>>> --
>>> Jean Louis Boudart
>>> Independent consultant
>>> Project Lead http://www.easyant.org
>>
>>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org
Re: Website
Posted by Jean-Louis Boudart <je...@gmail.com>.
I've initialized a draft, we still need a download page linking old release
before Apache Incubator.
Feedback are welcome
Le 9 mars 2011 13:42, Nicolas Lalevée <ni...@hibnet.org> a écrit :
>
> Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
>
> > It seems that we can't have a staging website [1] except if we use Apache
> > CMS.
> >
> > Now comes a few questions:
> >
> > - 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" ?
>
> 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.
>
> Nicolas
>
>
> >
> >
> >
> > 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
> >
> >> Looks good for me. I also think it would be great to have a staging
> >> website.
> >>
> >> 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 :
> >>
> >> - 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
> >>
> >> I created an issue for this (
> >> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
> >> there :p
> >>
> >>
> >>
> >> Le 28 février 2011 11:34, Nicolas Lalevée <ni...@hibnet.org>
> a
> >> écrit :
> >>
> >> Hi guys,
> >>>
> >>> (most of this email is quite a duplicate of the one I have done on
> >>> ant-dev)
> >>>
> >>> 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.
> >>>
> >>> 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.
> >>>
> >>> 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/.
> >>>
> >>> 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.
> >>>
> >>> 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
> >>>
> >>> WDYT ?
> >>>
> >>> Nicolas
> >>>
> >>>
> >>
> >>
> >> --
> >> Jean Louis Boudart
> >> Independent consultant
> >> Project Lead http://www.easyant.org
> >>
> >
> >
> >
> > --
> > Jean Louis Boudart
> > Independent consultant
> > Project Lead http://www.easyant.org
>
>
--
Jean Louis Boudart
Independent consultant
Project Lead http://www.easyant.org
Re: Website
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Le 9 mars 2011 à 11:55, Jean-Louis Boudart a écrit :
> It seems that we can't have a staging website [1] except if we use Apache
> CMS.
>
> Now comes a few questions:
>
> - 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" ?
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.
Nicolas
>
>
>
> 2011/2/28 Jean-Louis Boudart <je...@gmail.com>
>
>> Looks good for me. I also think it would be great to have a staging
>> website.
>>
>> 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 :
>>
>> - 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
>>
>> I created an issue for this (
>> https://issues.apache.org/jira/browse/EASYANT-19) and attached a draft
>> there :p
>>
>>
>>
>> Le 28 février 2011 11:34, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit :
>>
>> Hi guys,
>>>
>>> (most of this email is quite a duplicate of the one I have done on
>>> ant-dev)
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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/.
>>>
>>> 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.
>>>
>>> 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
>>>
>>> WDYT ?
>>>
>>> Nicolas
>>>
>>>
>>
>>
>> --
>> Jean Louis Boudart
>> Independent consultant
>> Project Lead http://www.easyant.org
>>
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Project Lead http://www.easyant.org