[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Propogating Changes to SVN Authorisation Policy

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-08-02 15:33:02 CEST

Please keep replies on the list.

On 8/2/06, Rama Mohan Rao Peruri <ramamr@dbs.com> wrote:
> Hi Andy,
> I understand and accept your point.
> I was just hoping to make some changes to the rights 'on the sly :-)
> :-)' and that users don't really realize the impact of the changes until
> it is too late.

You'll only annoy your users and foster feelings of distrust if you
try to "sneak" these kinds of things onto them. Just be open - let
everyone know that extra security is required for this directory and
you'll be locking it down, so please delete it from working copies.
Then, once it's locked down, change whatever sensitive information
(passwords?) that was contained in that directory so you're covered.

People are generally understanding of things like this if you're
honest and up-front with them. I just did a similar thing with our
external developer and he's actively involved with making changes that
are required as a result of him not being allowed access to a
directory - he's basically coding blind, under the assumption that
I'll set up the config files in this directory the way his code is
expecting to find them (he can't see these passwords, but the app
requires them).

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 2 15:34:47 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.