On May 18, 2:46 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > while i see the point you make, noah, not beeing able to freeze/tag/ > branch the wiki including the tickets, documents, and source code is > one of our major issues in getting more user acceptance for trac. > because first it is an idea or a ticket, then it should be documented. > and there should be a trace how things developed. so christians idea > has some appeal ... for us anyway.
I think it's useful to continue discussing ways to improve Trac's value as a documentation tool, but that shouldn't stop Noah & others' momentum on rewriting the documentation. Noah's efforts with Sphinx push us in the right direction for how we want to distribute the documentation, which is a separate issue from how we maintain it. Distributions should include a standalone set of documentation in HTML and/or PDF formats and be provided inside the application within a new Help module so that they're available even when the Wiki has been disabled. I also hope we can agree that the current free-for-all editing of the documentation in the t.e.o Wiki has become unsuitable for maintaining well-written docs. Moving them into the source tree with a more formal patch acceptance process should help that, so let's let Noah continue his current work and start a new discussion for how to improve Trac to the point where it's suitable for maintaining the docs at some point in the future. -- Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
