Re: Repository Access

[S I]

Thank you.  I suspected I had to or end up doing it from the unix admin 
level.  I thought (being a misguided person that I am ;) that like any other 
cvs task (such as notify, etc) you could simply create a text file and in it 
say something like:

#comment
address@hidden proj-A proj-B
address@hidden  proj-C only

So, looks like I have to create different unix groups, etc.  Thanks for the 
response.

Steve

----Original Message Follows----
From: Jim Hyslop <address@hidden>
To: S I <address@hidden>
CC: address@hidden
Subject: Re: Repository Access
Date: Thu, 16 Jun 2005 09:21:16 -0400
MIME-Version: 1.0
Received: from tomts25-srv.bellnexxia.net ([209.226.175.188]) by 
mc4-f30.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 16 Jun 2005 
06:21:22 -0700
Received: from [127.0.0.1] ([67.68.52.19]) by tomts25-srv.bellnexxia.net     
     (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP      
    id <address@hidden>;   
       Thu, 16 Jun 2005 09:21:21 -0400
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
References: <address@hidden>
Return-Path: address@hidden
X-OriginalArrivalTime: 16 Jun 2005 13:21:22.0999 (UTC) 
FILETIME=[4A686470:01C57276]

S I wrote:
> Hi Class!
>
> Currently our CVS repo has 3 main & separate projects running under it.  By 
> default when I create a new unix user; I give them access to the whole 
> repository, however, some folks have been editing files in projects they 
> were not supposed to.

> How can I ONLY and specifically create or modify the access rights & 
> privileges of only few specific people w/o wreaking havoc on the whole 
> repository?  And by default if they're not listed in that file then that 
> means they have access to all projs?  Is there a way?

Use your operating system's access control system. Create a group for each 
project, and assign people to the groups they are allowed to be in. You will 
have to determine, in conjunction with your project leaders, which projects 
new users will have access to, by default.

And, of course, get the managers and project leaders on side to explain that 
changing project files they haven't been assigned to will result in 
disciplinary action, up to and including termination.

--
Jim