[Trac] Using trac without source repository

Ryan Schmidt trac-2005 at ryandesign.com
Thu Feb 10 14:55:43 EST 2005


On 09.02.2005, at 16:23, Andrea aime wrote:

> Juanma Barranquero wrote:
>> Perhaps you could take a look at CVSTrac (http://www.cvstrac.org/)...
>
> Ok, I looked at it a bit more... I can't use it.
> I manage more than 20 projects in the same repository, with pserver
> authentication... I don't want to add a new pserver on a new port
> each time I need to add a project, and separately manage users
> We are few developers (10) and each one can see everything
> that the others are doing to get ideas and so on, having a different
> configuration for each different project is a mess for us.

Actually the single-project limitation is one of the reasons we're 
about to decide against using Trac. We are also ten developers working 
on many different projects for many different clients, but sharing 
ideas and libraries between them. We already have an issue tracker and 
a wiki, and we were considering replacing them with Trac, but if it 
means creating a separate Trac environment for each project, that 
seriously fragments our wiki experience, in which we currently also 
document things that don't relate to a specific project. As I 
understand it, Trac will continue to be a single-project-tracking 
system until Trac 2.0 which is probably still a long way off, seeing as 
we're only at 0.8 so far. And some people have suggested using the 
"Component" field as a "Project" field but then projects can't have 
components anymore (which may not be a huge deal) and all projects 
share the same list of versions (which seems to makes it unusable).

Or is there something I've missed?



More information about the Trac mailing list