Tapestry is so fun to use and develop, imho documentation should be as
well. I understand and agree with christian arguments, so i guess we
should vote for confluence for all the good reasons explained, but
this should not exclude to work on a fun and appealing front page.
Regards
Christophe Cordenier
Envoyé de mon iPhone
Le 4 mai 2010 à 23:06, "Thiago H. de Paula Figueiredo" <[email protected]
m> a écrit :
On Tue, 04 May 2010 17:26:27 -0300, Christian Riedel <[email protected]
> wrote:
I'd use confluence because:
- documentation can be added on-the-fly
This is very important, IMHO.
- fixes to older documentation is not dependent on the release of
the framework
- the infrastructure is already there
- more contributers could be allowed access to add documentation
This is very important, IMHO, even having a separate part for
official documentation. If someone writes a nice wiki page, we could
easily make it part of the official documentation.
- comments by users on documentation pages could help you to find
errors fast and others to get an alternative solution
I wasn't thinking of it and that's a very nice feature. Thanks
Christian!
...and jira's documentation is quite ok imho:
http://confluence.atlassian.com/display/ALLDOC/JIRA+Documentation+Directory
negative point is that everybody has to learn that confluence
syntax and nobody likes writing documentation anyway...
And also converting the current documentation. This would be a
problem for any solution besides keep on using the same tools we
already use (Maven).
+1 to Confluence.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer, and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
