Maybe we can think about a kind of documentation reference stored in the
svn repo (in the DocBook format for example). We can add the
documentation generation in the continuous integration process to
generate HTML/PDF.
Providing a more "professional" PDF user guide can be a skill.
Would you like that I raise a Jira task around this and begin the
documentation project structure ?
Regards
JB
Gert Vanthienen wrote:
Khaled,
I'm not sure projects about documentation would really get a lot of
attention, but you're absolutely right about the problems with our
documentation. Actually, I think the problem is twofold:
- some areas are probably really underdocumented and you can hardly
find anything about it on the website
- most things do have some kind of documentation, but the organisation
of the documentation is really bad
Especially for ServiceMix 4, the documentation seems to be all
scattered around: you'll find bits in the ServiceMix Kernel wiki, the
NMR wiki and for the components and the Maven tools you'll have to go
into the main ServiceMix (3) wiki/website.
With all that being said, we're particularly open to any kind of
suggestion on how to improve things (or even a helping hand ;) ).
Could you give us an overview of the information you were looking for
so we can figure out a way to get that together to start with or
something?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/3/31 Khaled Essghaier <[email protected]>:
Hi,
looks very interesting, i am a student actually and working actually in a
SOA project in which we are planning to use an ESB but i think that you
should consider projects related with the documentation and samples because
i got a hard time those couple of weeks trying to get something working with
SM4 which lead me to consider using open-ESB.
Regards,
*Khaled*
________________________________________________________
My blog = http://thepurplecows.blogspot.com/
