RE: Limiting Access

[Risman, Mark]

I don't know if this is the best way, but when we dealt with this issue here, we simply changed the permissions on the repository's root directory to be read-only. The effect of this was that in the instances that someone needs a new folder at the root level, they simply need to come to us (the CVS administrators) to create it for them. It effectively creates an approval process.

 

Yes, this means manually touching the repository, which we don't generally like to do. In this case, however, all we do is create the directory and nothing else. The users are able to do the rest.

 

---

From: address@hidden [mailto:address@hidden On Behalf Of Rez P
Sent: Wednesday, May 13, 2009 3:44 PM
To: CVS
Subject: Limiting Access

Hello Everyone
 
On the linux server at the root of my repository, I've created a top folder for each department whithin our company and each group is supposed to create new projects only under their own departmental folders. However, I'm finding that couple of developers created bunch of new projects directly on the root parallel to the other departmental folders, I'm planning to login to the server and move these folders to their appropriate place.  In the mean time, is there any way to limit access to the users as to where they can create new projects?
 
Thanks

---

Hotmail® has ever-growing storage! Don’t worry about storage limits. Check it out.

**********************************************************

MLB.com: Where Baseball is Always On