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.
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. :-) - 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. - 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) Though my primary intend is to use trac to earn money with my project, I would like to somehow support the project. Actively supporting an open source project will be my first time, though. Can not guarantee any amount of work or time, however, my project is supposed to run for about two years, meaning at least two years of trac (and other tools). I am not so much into coding nowadays (saw python sources for the first time in my life with the trac-digest.py), but feel a need for usable docs and proactive change management (almost 1,000 open tickets are way too many). To give you an idea about myself, a mini CV - German, born 1974, - Diplom-Informatiker (equals master in computer science) in 2001 - 1995 my first Linux PC (was 1.2.x) - Freelancer since 1998 - 2000-2003 developing telco and internet related SW (Unix, C++, Java) - 2004-2008 technical team leader of varying system test teams (3-14 Engineers) for several automotive electronic components (experience of managing about 2,000 bugs and a total of 4,000 change requests within those 4 years) - 2008- project manager and senior developer for a MS windows application rework. I really hope to see trac 1.0 before my new project is completed. I wish all of us enough time and motivation to continue work for and with this interesting tool. Viele Grüße, Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
