Sound great, Gert. +1
Regards Lars Am Montag, den 03.05.2010, 00:47 +0200 schrieb Gert Vanthienen: > L.S., > > We've been talking about creating a new DocBook-based manual for > ServiceMix in the past and we currently have two separate > proof-of-concepts sitting in the sandbox folder: > - Jean-Baptiste's sandbox folder has a skeleton ServiceMix 4.2.0 > manual, with some of the topics already filled in > - my own sandbox folder has a base project setup and an extra maven > plugin to allow (re)using Confluence markup and the snippets we have > in svn > > With some time available tomorrow, I would like to start moving all > this into a more definitive location so we can start collaborating on > the content. In my own proposal, I made a distinction between: > - a programmer's guide, which contains the real ServiceMix manual with > installation, configuration and development information > - a JBI Reference Guide, which contains the description of all the > endpoints with their options and a set of example configurations for > all of them to avoid cluttering the manual with all this information > > If that's OK for everyone, I'll keep this distinction for now and make > Jean-Baptiste's manual the first document (because he already has a > good table of contents for that kind of document), so all the work > that has already been done by him and Charles can be reused. > > For the svn layout, I would propose to create these two locations, > with svnmerge setup to merge docs from trunk into the branch: > - documentation/trunk for the current 4.x development version > - documentation/branches/servicemix-4.2.x for documenting the latest > release 4.2.0 > > The maven plugin can go into the maven-plugins project we already have > setup in Hudson -- I'll try to add a Hudson setup for the > documentation projects as well so they can get built/published > automatically. > > Regards, > > Gert Vanthienen > ------------------------ > Open Source SOA: http://fusesource.com > Blog: http://gertvanthienen.blogspot.com/
