Everything can be written into wiki, as long as they are well categorized.In practice, knowledge you want to share with your team, common documentation, contact information of your team, and so on.
On Mon, Aug 3, 2009 at 7:12 PM, xiechao <[email protected]> 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! > > > > -- =========================== Regards Ronghui Yu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
