From general-return-1794-apmail-logging-general-archive=logging.apache.org@logging.apache.org Sun May 20 20:29:34 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 5C4C8C67B for ; Sun, 20 May 2012 20:29:34 +0000 (UTC) Received: (qmail 33716 invoked by uid 500); 20 May 2012 20:29:34 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 33674 invoked by uid 500); 20 May 2012 20:29:34 -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 33665 invoked by uid 99); 20 May 2012 20:29:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 May 2012 20:29:34 +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 (athena.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; Sun, 20 May 2012 20:29:26 +0000 Received: from bigmax.localnet (unknown [82.231.48.193]) by smtp3-g21.free.fr (Postfix) with ESMTP id EB74BA6242 for ; Sun, 20 May 2012 22:28:58 +0200 (CEST) From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY To: Logging General Subject: Re: Logging web sites Date: Sun, 20 May 2012 22:28:57 +0200 Message-ID: <2019863.oGSPEhfnOM@bigmax> User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic; KDE/4.8.2; x86_64; ; ) In-Reply-To: References: <7F1F7665-D82D-4374-988C-F400A3610205@dslextreme.com> <6723759.HASrqZ9r3A@bigmax> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart3091469.kUFsjJLbft" Content-Transfer-Encoding: 7Bit X-Virus-Checked: Checked by ClamAV on apache.org --nextPart3091469.kUFsjJLbft Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" ok, so it's a custom rendering engine so I see 2 solutions: 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 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. 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. Regards, Herv=E9 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 --nextPart3091469.kUFsjJLbft Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

ok,= so it's a custom rendering engine

 

so = I see 2 solutions:

 

1. = either infra adds this engine as external, like it did with "mvn s= ite": you'll have to put sources in content, to trigger html gener= ation on each source update, buildbot will build the html, then you'll = use the CMS web interface to publish staged content

 

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

 

Wit= h 1st solution, main site is automatically published at each commit, ea= ch component being protected from erase by extpath.txt.

Wit= h 2nd solution, main site is manually published when somebody does it, = like components during releases, and you'll have to take care of not re= moving components content when publishing.

 

Reg= ards,

 

Her= v=E9

 

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

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

<= br />

R= alph

<= br />

O= n May 20, 2012, at 12:06 PM, Herv=E9 BOUTEMY wrote:

= I'm now subscribed to general@logging

T= hanks Ralph for INFRA-4669: it gives me good information on actual stat= us.

=A0=

T= he main question IMHO for the moment is: how are you planning to genera= te main site html? Maven, CMS's markdown, another tool?

T= hen each component will have its own generation tool, with the only exp= ectation is to output html to svn

=A0=

R= egards,

=A0=

H= erv=E9

=A0=

L= e 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= PMC. =A0However, I haven't done any work there in a very long time. =A0= This list would seem to be more appropriate for a logging related discu= ssion.


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


Ralph

=A0=


--nextPart3091469.kUFsjJLbft--