etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Fitzner <>
Subject AW: [DISCUSS] starting the CMS migration process
Date Thu, 20 Jan 2011 13:30:41 GMT
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
I also would like to change the website categories to the following structure (see below).
The documentation item/category 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 create the general website structure
and give feedback as soon it is ready. Afterwards we can start the migration of content together.

- Home 
- License 
- Downloads 
- FAQ 
- Security 
- Sitemap 

- Get Involved 
- Who we are 
- Mailing Lists 
- Bug Tracker 

- Source Code 
- Getting Started 
- Project Roadmap 
- (Performance) 

=> reference to manual 

- ASF 
- Sponsorship 
- Thanks


-----Urspr√ľngliche Nachricht-----
Von: scott comer [] 
Gesendet: Donnerstag, 13. Januar 2011 21:13
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 
is helping on how
to do this. the "expert" needs to be able to direct traffic and help the 
helpers when they get

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 
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:
> 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:
>> As mentioned at 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:
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>> --
>> Become a Wicket expert, learn from the best:

View raw message