This may be a dumb question but what does "jumping in #trac" refer to? I'm new :)
Currently I'm interested in how Trac's wiki engine works and how it's "source code browser" works. (I'm trying to see if I can wikify source code comments from the trac browser itself) Thank you! On Jun 4, 4:24 pm, "Noah Kantrowitz" <[email protected]> wrote: > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On Behalf Of David > > Sent: Friday, June 04, 2010 4:09 PM > > To: Trac Users > > Subject: [Trac] How does Trac actually work? > > > I'm running Trac right now and I was wondering since Edgewall doesn't > > post it if there exists a general methodology to how Trac works in > > theory. I'm looking for something image based like their workflow > > examples (http://trac.edgewall.org/browser/trunk/trac/htdocs/guide/ > > basic-workflow.png), but for the program itself. I've been running > > through the source code and I figure it's going to take me a while to > > map all of this out, so if anyone has already done this could they > > post their result? That would be wonderful! > > Edgewall is no longer an actual entity, it serves as a copyright umbrella in > the same way as the Pocoo project or the PSF (just a heads up). I think our > workflow on trac.edgewall.org is mostly the stock one, but Remy or CBoos > would know better. If you are talking about code layout, that is a bit too > complex for a single email but I would recommend jumping in #trac and asking > about the parts you are interested in. > > --Noah -- 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.
