Return-Path: Delivered-To: apmail-incubator-etch-dev-archive@minotaur.apache.org Received: (qmail 88793 invoked from network); 20 Jan 2011 13:31:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2011 13:31:31 -0000 Received: (qmail 52579 invoked by uid 500); 20 Jan 2011 13:31:31 -0000 Delivered-To: apmail-incubator-etch-dev-archive@incubator.apache.org Received: (qmail 51219 invoked by uid 500); 20 Jan 2011 13:31:28 -0000 Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: etch-dev@incubator.apache.org Delivered-To: mailing list etch-dev@incubator.apache.org Received: (qmail 50921 invoked by uid 99); 20 Jan 2011 13:31:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 13:31:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.245.222.98] (HELO mail.bmw-carit.de) (62.245.222.98) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 13:31:14 +0000 Received: from dc01.bmw-carit.intra ([192.168.100.4]:23734 helo=dc01.bmw-carit.de) by mail.bmw-carit.de with esmtps (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1Pfub5-0003KU-2p for etch-dev@incubator.apache.org; Thu, 20 Jan 2011 14:30:44 +0100 Received: from DC01.bmw-carit.intra ([fe80::c4d4:9ee6:b589:1e59]) by DC01.bmw-carit.intra ([fe80::d580:3d48:572:441%15]) with mapi; Thu, 20 Jan 2011 14:30:43 +0100 X-CTCH-RefID: str=0001.0A0B0206.4D383904.0021,ss=1,fgs=0 From: Michael Fitzner To: "etch-dev@incubator.apache.org" Date: Thu, 20 Jan 2011 14:30:41 +0100 Subject: AW: [DISCUSS] starting the CMS migration process Thread-Topic: [DISCUSS] starting the CMS migration process Thread-Index: AcuzXl6gt3zTot5WRRK+epwaImJnJwFMp6PA Message-ID: <66BD268F973E3544A665E5F503FB38B705C3A33EF5@DC01.bmw-carit.intra> References: <344297.12137.qm@web161403.mail.bf1.yahoo.com> <4D2F5CBD.7030901@mac.com> In-Reply-To: <4D2F5CBD.7030901@mac.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi Etch folk, I created some Jira Issues concerning our migration steps from our old Etch= website to new Apache CMS. The main Issue can be found here https://issues= .apache.org/jira/browse/ETCH-126. I also would like to change the website c= ategories to the following structure (see below). The documentation item/ca= tegory should consist of some generated Etch manual documents from docbook = (XSLT 2 html or markdown). All other content are special to the website and= should be written with html and markdown. While the next days I will creat= e the general website structure and give feedback as soon it is ready. Afte= rwards we can start the migration of content together. [General]=20 - Home=20 - License=20 - Downloads=20 - FAQ=20 - Security=20 - Sitemap=20 [Community]=20 - Get Involved=20 - Who we are=20 - Mailing Lists=20 - Bug Tracker=20 [Development]=20 - Source Code=20 - Getting Started=20 - Project Roadmap=20 - (Performance)=20 [Documentation]=20 =3D> reference to manual=20 [Foundation]=20 - ASF=20 - Sponsorship=20 - Thanks Regards, Michael -----Urspr=FCngliche Nachricht----- Von: scott comer [mailto:wert1y@mac.com]=20 Gesendet: Donnerstag, 13. Januar 2011 21:13 An: etch-dev@incubator.apache.org Betreff: Re: [DISCUSS] starting the CMS migration process the meta question is how to manage the process, who's doing what, etc. i would suggest once we have a good plan, that we need to train whoever=20 is helping on how to do this. the "expert" needs to be able to direct traffic and help the=20 helpers when they get stuck. is there perhaps a "quick and dirty" step which could be automated? perhaps creating jira issues for each page to be converted, so we don't=20 lose one? scott out On 1/13/2011 1:59 PM, Holger Grandy wrote: > Hi guys, > > for me the issue below is the final argument for integrating our > documentation into svn and to generate our website (or at least major > parts of it) > from there on. Michael has proposed docbook for this before christmas. > There are already some skeletons in trunk in the doc folder. > > Personally, I would be happy with full generation from svn. We have to > spent some effort on porting the current website content from > confluence > to this format. But this has to be done anyway when Apache is stopping > Confluence support. Is someone willing to start or support on this > topic? > I remember James, Scott and Younjun supported the idea in the etch-dev > thread from november. In the same thread Michael proposed an example > structure. > I would be happy if this effort could be continued now. Who is willing > to support this? Perhaps with porting some first documents from > confluence > to the new systen, perhaps with providing some good layout for the > generated site? > > Here is the thread from november: > http://mail-archives.apache.org/mod_mbox/incubator-etch-dev/201011.mbox/b= rowser > > Please post your comments, we need to get this moving forward. > > Thanks, > Holger > > On Tue, Jan 11, 2011 at 5:10 PM, Martijn Dashorst > wrote: >> This seems of interest since your website is generated out of >> confluence (according to my knowledge). >> >> Martijn >> >> ---------- Forwarded message ---------- >> From: Joe Schaefer >> Date: Tue, Jan 11, 2011 at 4:16 PM >> Subject: [DISCUSS] starting the CMS migration process >> To: general@incubator.apache.org >> >> >> As mentioned at http://www.apache.org/dev/cms.html the >> Infrastructure Team would like the IPMC to consider migrating >> to the CMS over the coming weeks. We will be completely >> phasing out support for Confluence backed sites this year, >> and would like to encourage all Apache projects still relying >> on Anakia (such as the Incubator) to migrate as well. This >> undoubtedly will impact current and new podlings. >> >> More information on the CMS is available at the following links: >> >> http://blogs.apache.org/infra/entry/the_asf_cms >> http://wiki.apache.org/general/ApacheCms2010 >> http://www.apache.org/dev/infra-site.html >> http://www.apache.org/dev/cmsref.html >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >>