Berin Loritsch wrote:
> Noel J. Bergman wrote:
> > If necessary, we can provide additional levels of control, e.g.,
> > if we wanted to give someone karma for the site without the
> > code, or if we had some need for a PMC-only area.  Details in
> > http://svn.collab.net/repos/svn/trunk/subversion/mod_authz_svn/INSTALL.

> We have the component repositories set up so that there is a greater
> access to both the James and Cocoon developers.  All Avalon
> developers should have access to all Avalon repositories, but we
> would only want the Cocoon and James developers to have access to
> the component repositories.

As I posted to your earlier:

  [groups]
  avalon=<list of avalon ids>
  avalon-pmc=<list of avalon pmc ids>
  cocoon=<list of cocoon ids>
  james=<list of james ids>
  members=<list of ASF member ids>
  ...

  [/]
  * = r
  @members = r

  [/avalon]
  @avalon = rw
  @avalon-pmc = rw

  [/avalon/pmc]
  * =
  @avalon =

  [/avalon/components/]
  @james = rw
  @cocoon = rw

  [/avalon/sandbox/]
  @james = rw
  @cocoon = rw

  [/avalon/excalibur/]
  @cocoon = rw

The above should give read-only access to everyone for everything except
where denied for /avalon/pmc, read access to members for everything,
read-write to avalon for /avalon except for /avalon/pmc, read-write to james
and cocoon for specific areas, and read-write access to only the Avalon PMC
for the PMC area.

Just trying to give an idea of the flexibility of the system.

        --- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to