On Jun 5, 1:50 am, David <[email protected]> wrote: > This may be a dumb question but what does "jumping in #trac" refer to?
He means the IRC channel, please see [1] for more information. I think your original question about the documentation of Trac is very relevant. I'm in the same situation like you -- new -- and would also appreciate some good food for thoughts. However, this kind of work is normally very hard to do. One could use a UML tool or alike to reverse-engineer the code to get an overview (after slicing away multitudes or overly detailed diagrams), but such methods seldom yields qualitative results worth keeping, less distributing (okay, I'm pretty sure some may have opinions against this statement) and the correctness tends to degrade as the code is evolving. So, the best would be if a core developer writes down the design on an architectural level, i.e. not too detailed but enough to understand where to dig around. But there are quite a lot of good information on the TracDev page to get started [2]. I would like to say that my request has actually started, and it's up to us all to dive in and help. I've been seriously considering modelling the design in a UML tool -- I'm an expert in that area -- but I'm holding back for many reasons, some already stated above. The main problem in documenting the design this way is how to transfer the result to others for enhancements? Contrary to good project control tools as Trac, usable UML tools are not for free... UML and open-source just doesn't match yet... (please enlighten me, anyone, if you think I am wrong). [1] http://trac.edgewall.org/wiki/IrcChannel [2] http://trac.edgewall.org/wiki/TracDev Best regards, Mikael Relbe -- 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.
