Michael Stratmann wrote: > Hello everybody, > > Having acquired my first commercial project where I can decide on > processes and tools, I intend to use trac for documentation and change > management :-) For config management I will try using Mercurial. I > decided for trac because of the close integration of doc, chng and > conf mngmnt. >
Good pick ;-) The Mercurial support has still many opportunities for enhancements, but it should be OK for medium sized projects. If you need to handle several repositories at onces, be sure to have a look at the http://trac.edgewall.org/wiki/MultipleRepositorySupport. > My first experiences (trac only): > Not having a Linux PC at hand right now, I started installing trac on > my WinXP work station, after reading all kinds of trac docs for about > a day. > - I managed to get trac run within some minutes. :-) > Great! > - It took me about two hours two have a proper user with admin > rights :-( When I had it running I found the important clue in the > documentation. > I think somebody already suggested that we add some hints about this on WikiStart... wait, its already there in 0.11. Maybe not visible enough? > - It took me another two hours to get the Account Manager running, > though I am not sure if I will really need it. Again I got lost in > documentation (why, how?). > > - The basic documentation for the core and the plug ins seem not so > cleaned up. Esp. they appear to suffer from t.e.o and t-h.o being > split. > - This being my first time being admin of a wiki and a change > management system, I really miss some examples and best practices on > how to set up stuff in a good way. > - Some docs were correct, but had confusing structure (I do not have > apache, but use tracd, tough to read around the apache stuff all the > time) > In the future, when you'll get more intimate with Trac, you could greatly help the project by writing documentation or reviewing what gets written. But it's quite useful to have a "newcomer's" eye on the matter, as for documentation writers, it's easy to forget what you can't possibly know when you start up with a project, once you know that project by heart. So I'd suggest that you take some notes from your fresh experience, listing the pitfalls you've encountered and what you would have expected to find. In any case, thanks for your interest in Trac! -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
