Martin Tomes said the following on 01/23/2006 10:46 AM: > We require support for multiple projects in Trac and I started a page on > this some time ago. My proposal for how to implement this is described > here: > > http://projects.edgewall.com/trac/wiki/TracMultipleProjects/ByProductAndSearch > > > If an implementation of this feature can be agreed with the project > maintainers and accepted into the Trac code base we would commit one > person for six months to implement this. Getting this code accepted into > the Trac code base is important to us, and as this feature is on the > roadmap this should be possible. > > Please take my proposal as a starting point - any ideas which would make > it better and or easier to do are very welcome. If there is anyone out > there who is willing to help with this we would appreciate assistance. > > The person who will be doing this doesn't speak Python yet so there will > be a period at the start of the project allocated to learning Python and > getting to grips with the internal workings of Trac. > > Your comments please!
I run trac for a client with several trac projects with a 1-2-1 relation to svn repos (1 repo = 1 trac project). The main issue we have with it is the (lack of) the ability to produce summaries across all projects (all oustanding tickets, all new tickets this period, checkins this month, etc. etc.). So, from my perspective, if it was possible to create an "master" trac project which could view all details from many "sub" trac projects then I'd be happy. R, _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
