#2086: better support for multiple repositories
-------------------------+--------------------------------------------------
 Reporter:  anonymous    |        Owner:  cboos   
     Type:  enhancement  |       Status:  assigned
 Priority:  normal       |    Milestone:  0.11    
Component:  browser      |      Version:  devel   
 Severity:  normal       |   Resolution:          
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by [EMAIL PROTECTED]):

 This is interesting. I'm looking for ways to make Trac more "forge-like",
 basically to create some kind of community around multiple Trac
 environment on a single install.

 For me, the default "listing of projects" when you access the root of the
 trac install could be a trac itself, with its own wiki, templates and
 bugtracker. It could have special plugins for tracking project and user
 activity, as gforge does for example.

 I would be interested in finding ways of making this a reality in Trac. We
 would like to start a forge here, but I find gforge has a ... well...
 charged history and is a bit bloated. I like the minimalist "no bullshit"
 approach trac has.

 For me the main issues to make this work at this point are:

  1. have a way for the account manager plugin to manage apache or
 authz_svn "groups", the same way it currently manages user accounts. this
 is critical to have credentials isolation from a project to the other
  2. make the "root trac listing" be a bit more fleshed out. this can be
 either:
    1. by making that a mostly "static" (as in not modifiable without
 hacking the source) content that would display projects statistics
    2. by making that a complete trac install with custom plugins for
 activity

 As for the original idea of the bug, I think a simple solution would be to
 allow InterWiki linking through the difference projects. Just prefix the
 usual links by the project name and you're done. So for example, you have
 2 projects environment on your trac install: projecta and projectb.

  * to link to a wiki page, you simply use: projecta:WikiStart or
 projectb:WikiStart
  * to link to a bug: projecta:#349
  * to link to a file: projecta:source:trunk/
  * to link to a revision: projecta:[1234]
  * etc...

 Wikis have been networked like this forever and it works like a charm.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/2086>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to