Michiel Meijers wrote:
> In my development team we have a discussion on where to store
> documentation of the development project. Some say that we should only
> write documentation on the TracWiki if we want to show it online for
> our customers, and that all other (i.e. internal) documentation (like
> designs, build guides) should be written in HTML/RTF/whatever and be
> stored in a specific Subversion subfolder. In my opinion, everything
> should either be stored as HTML/RTF/whatever in Subversion or as
> TracWiki.
>
> Any ideas, opinions, or links to other writings?
Similar situation here, but we only have a library to take care of, so
only programmers to deal with, which lessens the formatting
requirements a little bit.
Our current plan is to have the API docs generated by doxygen (and
integrated into Trac using the doxygen plugin) and have
conceptual/textual documentation as a Wiki subtree. To connect the two
we want to write some Macros for doxygen that know about the Wiki, and
make the doxygen plugin search a little more flexible. I did some basic
work on that but haven't gotten around to doing the full thing.
If anybody is doing similar things, I'd be interested in hearing about
them. What we would like to do but haven't quite figured out is how to
turn the Wiki subtree into a PDF document for off-line reading...
Dirk
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---
