> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Remy Blank
> Sent: Thursday, June 04, 2009 2:11 PM
> To: [email protected]
> Subject: [Trac-dev] Re: [Trac] Documentation thoughts
>
> Noah Kantrowitz wrote:
> > The other limitation of our wiki is that we cannot easily "branch" as
> > you would in subversion.
>
> I agree with that. Keeping the 0.11/... and 0.12/... hierarchies in the
> wiki in sync seems to be more difficult than it should be.
>
> > Docs are no different than code. If you (a community member) want to
> > change the docs, open a ticket and submit a patch as with anything
> > else. This allows for tight control over what goes in and allows us
> to
> > be sure we trust what goes in.
>
> I fully agree as well.
>
> > As we discussed earlier, ReST/Sphinx brings a powerful toolchain with
> > it that we have no equivalent of. Sure we could take the time to
> clone
> > all of that to work with Trac wiki markup, but I really don't see the
> point.
>
> To be honest, I don't see the need either. ReST/Sphinx may be powerful,
> but that power is not needed for the Trac guide, which is mostly static
> pages and a few macros like [[TracIni]]. So I see no obvious benefit to
> moving to ReST for the TracGuide, while the higher barrier to entry is
> a drawback.
Two primary counter-points: PDF generation and automated index generation.
Both are very useful even for user docs.
--Noah
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
