[p4] Managing groups of users

[Chuck Karish]

At 08:50 AM 10/10/00, John Griffin wrote:
>Hi all,
>in the development process we are using we need to, at the end of the
>development cycle, lock down a branch and only let people update it when
>they have been given leave to do so. I have accomplished this by removing
>all write privileges from the branch and then grant write access to an
>individual only when they need it. The system works quite well but I can see
>a problem with scalability; when there are more and more development streams
>to be locked down I will spend more and more of my time denying and granting
>people access to update branches. It also places me, the super user, in the
>critical path of an update.

This is a scaling problem for the development process as a whole,
not just for SCM.

We give superuser privileges to project leads so they can manage access
to their own lines.  The SCM admins set up group access and the code
line owners controls group membership for their respective lines.

>Is there a better way to do this? If not is there a means to allow others to
>give write access to a branch without giving them super user access?

We're under an honor system anyway not to step on each others' code.
There haven't been problems with abuse of privileges.
--
    Chuck Karish               BEA Systems
    karish at bea.com             San Francisco, CA
    (415) 317-0182 (cell)      (415) 402-7692