Hey guys,
first off let me congratulate you for a very productive meeting and
share the true excitement I get when I see such "open source miracles"
happening :)
Then my 0.02€ especially on how can documentation process:
On Apr 14, 2010, at 3:54 PM, Florian Müller wrote:
Here is an update on the current state of the discussion.
Merge process:
* It's in SVN: /incubator/chemistry/opencmis/trunk/
Release:
* We'll try to kick off a release process when the code merge has
been finished.
That should be in about 2-3 weeks.
* Florent will be the release manager for that release.
* We want to include some of the Wiki pages as documentation into
the release packages.
Nice, as the chosen groupId is org.apache.chemistry.opencmis, Florent
should have no problem in deploying to repository.apache.org with the
usual ASF credentials.
Chemistry web site:
* We would like to make an exported version of the Confluence Wiki
the main Chemistry web site.
* The landing page should list all Chemistry sub projects and have
links to the documentations.
* Stephan and Paul will set it up (templates, navigation, etc.).
* Dave will work on the layout (CSS, graphics, etc.).
So, does this mean we want to manage it :
1. manually?
2. with some kind of server side framework?
3. (a strong +1 for me here) using the standard maven site /
documentation process [0] ?
In case we choose for option 3, the list of activities for the site
can be broke down as:
* Using the Maven Doxia Confluence input module [1] to input current
pages exported from Confluence. Lately, if we like it, Confluence can
still be used for writing docs that can be fed into Maven _baseline_
by the means of a copy paste.
* A multimodule menu is automatically generated in a maven multimodule
site. As a personal experience, the maven site features have largely
improved lately also in this sense.
* Creating a site.xml defining the site structure [2] and navigation.
* Graphics and style can be aggregated in a maven site skin [3]. We're
nicely using this feature for another project (Spring Surf [4]), using
the SpringSource skin.
Of course the whole thing integrated in the maven release process.
I mostly willing to help out on this if you think it's worth, as I
believe it *definitely* makes sense to give a well known unified and
integrated single point of contact to our community,
reflecting the great efforts done on the code side :)
Thanks again for the great job and for keeping us posted!
Gab
[0] http://maven.apache.org/guides/mini/guide-site.html
[1] http://maven.apache.org/doxia/modules/index.html#Confluence
[2] http://maven.apache.org/guides/mini/guide-site.html
[3]
http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html
[4]
http://www.springsurf.org/sites/1.0.0.M3/spring-surf-devtools/spring-surf-doc-plugin/index.html
- Florian
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
