On Aug 3, 4:12 am, xiechao <xiecha...@gmail.com> wrote: > Hi: > Now I'am in charge of a media-sized project (above 100 > man*month) and we decide to adopt the agile developement way (since we > are not completely sure of the requirements yet), I've worked with > trac in a small project before, but what happens now is every body > just scratch on the wiki at will and the wiki finally is in such a > mess. The the question is: in practice, What should be written on the > wiki and what should not? Besides, we use UML(in EA or rose) as well > (after all, we are not running an opensource project) and there must > be some documents conforming to the company's standard. I don't want > to waste too much energy to keep the documents and trac synchronized. > Anybody has suggestions? Thanks very much!
Two ideas for you: 1. Create Page Templates for your wiki pages [1] 2. Use the WebSequenceDiagramPlugin [2] to draw UML diagrams on the wiki [1] http://trac.edgewall.org/wiki/PageTemplates [2] http://trac-hacks.org/wiki/WebSequenceDiagramPlugin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
