[Trac] Fancy permissions?

[Peter Fein]

Hiya-

I'm trying to figure out how to configure Trac to meet my needs.  I'm
really looking forward to using it - should be a lot more effective than
 my current setup (CVS/emails sitting in my inbox).

A little background: I've got a core group of developers who will have
full access to the system.  We also have a few outside contractors who I
want to prevent from viewing most of the source/bugs/wiki pages. The
contractors do require support from / interaction with the in-house
developers.  I'd like to keep things as integrated as possible to keep
life simple.

I'm unclear if Trac can do permissions for the repository browser.  No,
according to:
http://projects.edgewall.com/trac/wiki/TracBrowser

but yes, according to:
http://projects.edgewall.com/trac/wiki/FineGrainedPermissions

Which is correct? Is there similar support for issues/wiki pages?

Based on the docs, the permissions seem to be more like roles -
view/edit *ALL* bugs, etc., rather than on a per-bug basis.  It'd be
nice to restrict access to bugs based on component, assignee/reporter or
CC. I'm a little less clear what this would mean for wiki pages.

Is this doable?  Any suggestions on how to make this happen (perhaps
with macros)?  My best thought ATM is to set up two projects pointing to
the same repository - one for internal use only & one for use by both
in-house developers and contractors.  Less than ideal...

-- 
Peter Fein                 pfein at pobox.com                 773-575-0694

Basically, if you're not a utopianist, you're a schmuck. -J. Feldman