I’ve browsed the wiki and FAQ and didn’t see much if anything on this;
please accept my apologies the answers to all these issues are out
there and I just missed it. And if putting up a ‘manual_meta’ page
on the wiki is the best way to proceed, I’ll happily do it.
We’re looking at RT for possible use for our in-house trouble ticket
system. Part of the decision process is the quality of the docs and
how we can maintain and modify them to match our local customizations
of RT.
Jesses comments on the list refer to a RTF format version of the
manual. Assuming this means ‘Rich Text Format’, I’d like to get my
hands on the draft manual source. If it doesn’t mean richtext, what
is the manual source written in?
There are a number of meta-issues about the manual and docs that probably
apply to more than just us. I’d be interested in folks’ opinions and
current or planned actions on any of the following:
Do you customize the docs to match your local customizations, and if
so, how?
Are the docs in any sort of source control system (CVS, bitkeeper,
subversion, etc)? Or is the wiki system the sum total?
Is there a plan for maintaining back-versions of the wiki manual for
those who stick with earlier versions (3.0) of RT?
On simultaneously tracking RT progress and RT customizations – how
do folks who’ve made localized versions of the docs keep their local
changes in sync with the broader flow?
FYI, don’t expect a whole lot of response from me immediately. I’m
pushing off for vacation tomorrow morning and won’t be reading email.
Advance thanks,
Steve Simmons
