tortoise/svn question

[bruce <be...@earthlink.net>]

hi...

i can setup a svn repository to allow users to access the underlying
folders/files. i can allow users to access the repository using tortoiseSVN.

a possible structure is:
 trunk
   dev
     file1
   rev
   test

or
 trunk
     file1

i'm trying to determine which setup makes sense...

my goal is to allow certain users to be assigned certain roles
(dev/rev/test). this allows me to create a simple/basic kind of workflow for
the file/script. only users with the given role would have the right to
access/modify/check (in/out) the file.

if i use separate folders, with each subfolder maching the role, it gets to
be easy. i can simply copy the file to the next folder, and restrict the
access rights to the folder to the given user in the access file. this model
would work with tortoiseSVN fairly easily.

if i use only one file, then i'm not sure how much underlying/behind the
scenes manipulation of the user access file i'd have to do as a user
modifies the script file. if someone with a dev role modified the file, i'd
have to then go into the access file, and change the access rights to remove
the person with the dev rights, and add the person with the rev rights...

is there another possible way that i'm missing...

thanks

bruce
bedouglas@earthlink.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: tortoise/svn question

[Nico Kadel-Garcia <nk...@comcast.net>]

bruce wrote:
> hi...
>
> i can setup a svn repository to allow users to access the underlying
> folders/files. i can allow users to access the repository using
> tortoiseSVN.
>
> a possible structure is:
> trunk
>   dev
>     file1
>   rev
>   test
>
> or
> trunk
>     file1
>
> i'm trying to determine which setup makes sense...
>
> my goal is to allow certain users to be assigned certain roles
> (dev/rev/test). this allows me to create a simple/basic kind of
> workflow for the file/script. only users with the given role would
> have the right to access/modify/check (in/out) the file.
>
> if i use separate folders, with each subfolder maching the role, it
> gets to be easy. i can simply copy the file to the next folder, and
> restrict the access rights to the folder to the given user in the
> access file. this model would work with tortoiseSVN fairly easily.
>
> if i use only one file, then i'm not sure how much underlying/behind
> the scenes manipulation of the user access file i'd have to do as a
> user modifies the script file. if someone with a dev role modified
> the file, i'd have to then go into the access file, and change the
> access rights to remove the person with the dev rights, and add the
> person with the rev rights...
>
> is there another possible way that i'm missing...

I think so. By using appropriately named branches, such as:

    branches/rev/file1
    branches/dev/file1
    branches/rev/file1

And when you're ready, merge or copy them to

    trunk/file1

You can achieve the same result without the debris in trunk, and trunk 
becomes the "reference copy" it's normally used as. 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org