From general-return-1802-apmail-logging-general-archive=logging.apache.org@logging.apache.org Tue May 22 06:37:19 2012 Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A658DCDBA for ; Tue, 22 May 2012 06:37:19 +0000 (UTC) Received: (qmail 11496 invoked by uid 500); 22 May 2012 06:37:18 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 11345 invoked by uid 500); 22 May 2012 06:37:17 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 11312 invoked by uid 99); 22 May 2012 06:37:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 06:37:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [212.27.42.3] (HELO smtp3-g21.free.fr) (212.27.42.3) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 06:37:05 +0000 Received: from bigmax.localnet (unknown [82.231.48.193]) by smtp3-g21.free.fr (Postfix) with ESMTP id 3212DA6308 for ; Tue, 22 May 2012 08:36:38 +0200 (CEST) From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY To: Logging General Subject: Re: Logging web sites Date: Tue, 22 May 2012 08:36:37 +0200 Message-ID: <1614222.QUupXQk5g3@bigmax> User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic; KDE/4.8.2; x86_64; ; ) In-Reply-To: <592E850E-544E-48B8-857F-190122035757@dslextreme.com> References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <10789995.YStjn4EZiv@bigmax> <592E850E-544E-48B8-857F-190122035757@dslextreme.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart16517001.jx0Q8lyDXf" Content-Transfer-Encoding: 7Bit --nextPart16517001.jx0Q8lyDXf Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" oh, yes, sorry, I described option 2. Then option 1 will require infra to work on integrating your templating= engine=20 as external task : someone knowing this engine, its prerequisites and s= o on=20 has to work with infra to help them run the tool by hand then be able t= o=20 launch it from build system (with source files in content directory, ou= tput=20 directory set by a command line attribute) Notice that if you explain infra that /whatever/file.html is generated = from=20 /content/pages/file.twig, it should be easy for infra to add support fo= r online=20 content editing =3D a really nice feature of the CMS. You can even add= a "CMS=20 boormarklet" in your bookmarks, and jump into content editing in one cl= ick=20 from browse. This one is very nice. If this is not clear, I can explain= more=20 this feature, because the "CMS bookmarklet" isn't something everybody k= nows. Regards, Herv=E9 Le lundi 21 mai 2012 23:11:47 Ralph Goers a =E9crit : Wait - I thought option 1 used the CMS and could invoke the site build.= Ralph On May 21, 2012, at 1:55 PM, Herv=E9 BOUTEMY wrote: seems a good step, IMHO, because your main site has its own templating = engine=20 that won't be used by many people, then don't deserve CMS dedicated cod= e to=20 integrate it: pure svnpubsub will be the simplest choice for everybody =20 and as done in the main site source, a pom.xml can provide html publish= to=20 svn: just need to check if excludes works well to avoid deleting compon= ents=20 subsites when publishing main site update =20 Regards, =20 Herv=E9 =20 Le dimanche 20 mai 2012 15:15:46 Ralph Goers a =E9crit : Based on your other answers I'm in favor of going with option 1. I thi= nk we=20 should start by having infra set up a loggingtest site. and then see if= we=20 can't get Ivan's build to work (preferably in English). Ralph On May 20, 2012, at 1:28 PM, Herv=E9 BOUTEMY wrote: ok, so it's a custom rendering engine =20 so I see 2 solutions: =20 1. either infra adds this engine as external, like it did with "mvn sit= e":=20 you'll have to put sources in content, to trigger html generation on ea= ch=20 source update, buildbot will build the html, then you'll use the CMS we= b=20 interface to publish staged content =20 2. either infra simply adds svnpubsub, without any CMS integration, ie = any=20 source modification integration nor html build from sources. I don't kn= ow if=20 they do that. But that way, you're completely free, you only use svnpub= sub:=20 it's up to you to get the tooling to put html content to svn. =20 With 1st solution, main site is automatically published at each commit,= each=20 component being protected from erase by extpath.txt. With 2nd solution, main site is manually published when somebody does i= t, like=20 components during releases, and you'll have to take care of not removin= g=20 components content when publishing. =20 Regards, =20 Herv=E9 =20 Le dimanche 20 mai 2012 12:53:27 Ralph Goers a =E9crit : Here was what Ivan proposed - http://mail- archives.apache.org/mod_mbox/logging- general/201205.mbox/ajax/%3CCAKpWnhTiVEe0M54UOFHGXTUOPq3TX2Jd_Z- a7B9H_pfnxQmCDg%40mail.gmail.com%3E Ralph On May 20, 2012, at 12:06 PM, Herv=E9 BOUTEMY wrote: I'm now subscribed to general@logging Thanks Ralph for INFRA-4669: it gives me good information on actual sta= tus. =20 The main question IMHO for the moment is: how are you planning to gener= ate=20 main site html? Maven, CMS's markdown, another tool? Then each component will have its own generation tool, with the only=20= expectation is to output html to svn =20 Regards, =20 Herv=E9 =20 Le dimanche 20 mai 2012 11:58:16 Ralph Goers a =E9crit : If you meant me, of course I'm subscribed to Maven Dev as I'm on the PM= C.=20 However, I haven't done any work there in a very long time. This list= would=20 seem to be more appropriate for a logging related discussion. To reiterate a bit for Herv=E9's sake, I've=20 opened https://issues.apache.org/jira/browse/INFRA-4699 which is sort o= f in a=20 state of limbo waiting for us to tell infra what we actually want. We h= aven't=20 responded because we aren't really sure. So the first piece we need is=20= something to tell infra so that we can actually start doing something. Ralph =20 --nextPart16517001.jx0Q8lyDXf Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

oh,= yes, sorry, I described option 2.

 

The= n option 1 will require infra to work on integrating your templating en= gine as external task : someone knowing this engine, its prerequisites = and so on has to work with infra to help them run the tool by hand then= be able to launch it from build system (with source files in content d= irectory, output directory set by a command line attribute)

 

Not= ice that if you explain infra that /whatever/file.html is generated fro= m /content/pages/file.twig, it should be easy for infra to add support = for online content editing =3D a really nice feature of the CMS. You c= an even add a "CMS boormarklet" in your bookmarks, and jump i= nto content editing in one click from browse. This one is very nice. If= this is not clear, I can explain more this feature, because the "= CMS bookmarklet" isn't something everybody knows.

 

Reg= ards,

 

Her= v=E9

 

Le = lundi 21 mai 2012 23:11:47 Ralph Goers a =E9crit :

Wait - I thought option 1 used the CMS and could invoke the site build= .

<= br />

R= alph

<= br />

O= n May 21, 2012, at 1:55 PM, Herv=E9 BOUTEMY wrote:

seems a good step, IMHO, because your = main site has its own templating engine that won't be used by many peop= le, then don't deserve CMS dedicated code to integrate it: pure svnpubs= ub will be the simplest choice for everybody

=A0

and as done in the main site source, a = pom.xml can provide html publish to svn: just need to check if excludes= works well to avoid deleting components subsites when publishing main = site update

=A0

Regards,

=A0

Herv=E9

=A0

Le dimanche 20 mai 2012 15:15:46 Ralph = Goers a =E9crit :

Based on your other answers I'm in = favor of going with option 1. =A0I think we should start by having infr= a set up a loggingtest site. and then see if we can't get Ivan's build = to work (preferably in English).

<= span style=3D" font-size:medium;">

<= span style=3D" font-size:medium;">Ralph

<= span style=3D" font-size:medium;">

<= span style=3D" font-size:medium;">On May 20, 2012, at 1:28 PM, Herv=E9 = BOUTEMY wrote:

ok, so it's a custom rendering engine<= /span>

=A0

so I see 2 solutions:

=A0

1. either infra adds this engine as ext= ernal, like it did with "mvn site": you'll have to put source= s in content, to trigger html generation on each source update, buildbo= t will build the html, then you'll use the CMS web interface to publish= staged content

=A0

2. either infra simply adds svnpubsub, = without any CMS integration, ie any source modification integration nor= html build from sources. I don't know if they do that. But that way, y= ou're completely free, you only use svnpubsub: it's up to you to get th= e tooling to put html content to svn.

=A0

With 1st solution, main site is automat= ically published at each commit, each component being protected from er= ase by extpath.txt.

With 2nd solution, main site is manuall= y published when somebody does it, like components during releases, and= you'll have to take care of not removing components content when publi= shing.

=A0

Regards,

=A0

Herv=E9

=A0

Le dimanche 20 mai 2012 12:53:27 Ralph = Goers a =E9crit :

Here was what Ivan proposed -=A0http://mail-archives.apache.org/mod_mbox/= logging-general/201205.mbox/ajax/%3CCAKpWnhTiVEe0M54UOFHGXTUOPq3TX2Jd_Z= -a7B9H_pfnxQmCDg%40mail.gmail.com%3E

<= span style=3D" font-size:medium;">

<= span style=3D" font-size:medium;">Ralph

<= span style=3D" font-size:medium;">

<= span style=3D" font-size:medium;">On May 20, 2012, at 12:06 PM, Herv=E9= BOUTEMY wrote:

= I'm now subscribed to general@loggin= g

<= span style=3D" font-size:medium;">Thanks Ralph for INFRA-4669: it gives= me good information on actual status.

<= span style=3D" font-size:medium;">=A0

<= span style=3D" font-size:medium;">The main question IMHO for the moment= is: how are you planning to generate main site html? Maven, CMS's mark= down, another tool?

<= span style=3D" font-size:medium;">Then each component will have its own= generation tool, with the only expectation is to output html to svn

<= span style=3D" font-size:medium;">=A0

<= span style=3D" font-size:medium;">Regards,

<= span style=3D" font-size:medium;">=A0

<= span style=3D" font-size:medium;">Herv=E9

<= span style=3D" font-size:medium;">=A0

<= span style=3D" font-size:medium;">Le dimanche 20 mai 2012 11:58:16 Ralp= h Goers a =E9crit :

If you meant me, of course I'm su= bscribed to Maven Dev as I'm on the PMC. =A0However, I haven't done any= work there in a very long time. =A0This list would seem to be more app= ropriate for a logging related discussion.


To reiterate a bit for=A0Herv=E9's = sake, I've opened=A0https://issues.apache.org/jira/browse/INFRA-469= 9=A0which is sort of in a= state of limbo waiting for us to tell infra what we actually want. We = haven't responded because we aren't really sure. So the first piece we = need is something to tell infra so that we can actually start doing som= ething.


Ralph

<= span style=3D" font-size:medium;">=A0








--nextPart16517001.jx0Q8lyDXf--