The tags plugin is very useful in doing this. You can use it to make a pretty good document workflow in the wiki. Overall this is not the same as a "real" document management system, in the same way that the Trac tracker has fewer features than Bugzilla, and the wiki fewer than Mediawiki. If those extra features are something you wouldn't use anyway, then the reduction in complexity is often nice.
--Noah On Aug 14, 2007, at 4:44 PM, [EMAIL PROTECTED] wrote: > > Would you say that trac has a good document repository. I have only > been using the online demo of trac and have not done and install on my > own computer. From what I can see so far it looks like Trac is mostly > oriented towards tracking the implementation and QA cycles ...which > makes sense for a bug tracking utility of course. But how would you > say it is for requirements and design phase ? I'd like to have use > case docs, functional specs, design docs all flow into tickets for > implementation, enhancement and bugs. Any knowledge about Trac as a > document repository and how it works would be helpful. So far I've > only seen that I can use "view source" to go into subversion and pull > out docs that way. > > thanks much. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
