We've got several groups of developers at different geographical
locations and we'd like for them to all work out of the same code base.
Problem is, this needs to be done in a very secure manner.

We currently have our code repositories using SVN.

Anyone have ideas on how this might be done or where I could find more
information on this?

On 31 Oct 2005, "Wizumwalt@gmail.com" <Wizumwalt@gmail.com> wrote:

> We've got several groups of developers at different geographical
> locations and we'd like for them to all work out of the same code
> base. Problem is, this needs to be done in a very secure manner.
> 
> We currently have our code repositories using SVN.
> 
> Anyone have ideas on how this might be done or where I could find
> more information on this?

Use Subversion but through a VPN or SSH tunnel.

Dave

-- 
D.a.v.i.d  T.i.k.t.i.n
t.i.k.t.i.n [at] a.d.v.a.n.c.e.d.r.e.l.a.y [dot] c.o.m

Ok, sorry, I guess I didn't explain that right.

I'm wondering about how to get different groups to sync up on using the
same code base. I have questions about whether or not to use separate
repositories and is there an easy way to merge the repository code once
a day, or should we all be working out of the same repository, just
different ways on how groups located in different places should manage
code.

And what about groups that have read only perms? How should they submit
code and to whom?

Wizumwalt@gmail.com wrote:
> Ok, sorry, I guess I didn't explain that right.
>
> I'm wondering about how to get different groups to sync up on using the
> same code base. I have questions about whether or not to use separate
> repositories and is there an easy way to merge the repository code once
> a day, or should we all be working out of the same repository, just
> different ways on how groups located in different places should manage
> code.

If it is the same code base, seems like one repository should be the
ideal.
>
> And what about groups that have read only perms? How should they submit
> code and to whom?

What changes would a read-only group (I'm guessing something like the
Test group) be submitting? They should not be changing code. Sounds
like you need  a problem tracking/reporting system too.

ed

They will be able to checkout the code, build and run it, but if they
want to make changes, my guess is that they would submit the changes to
someone that has the perms, like a lead developer. I'm just thinking of
how *I think* open source implementations are done today, like on
sourceforge.

Just trying to get ideas on best practices of how this would be done
for non-open source implementations.

<Wizumwalt@gmail.com> wrote in message
news:1130880241.464742.207810@f14g2000cwb.googlegroups.com...
> They will be able to checkout the code, build and run it, but if they
> want to make changes, my guess is that they would submit the changes to
> someone that has the perms, like a lead developer. I'm just thinking of
> how *I think* open source implementations are done today, like on
> sourceforge.
>
> Just trying to get ideas on best practices of how this would be done
> for non-open source implementations.

We're not open source, and we don't use subversion (but it
has similar features to what we use, I believe). Generally,
most of our developers have access to everything - we trust
them to stay out of stuff they don't understand. However,
we do have a few restricted areas.

A non-authorized developer wanting to make changes to those
areas can branch them to their own sandbox branch, check out
from there, and submit all they want. They could then ask
someone with access to the restricted area to review their
changes and merge them if they're approved.

The same thing can be applied, generally, to any branch or
path that needs some restrictions on changes. Create an
open development branch and promote selected changes from
there to the "gold" branch. (Only a few senior developers
would have this ability.)

As I understand subversion, it should manage this pretty
well. -Wm

I don't think I follow the subscription system. What's the difference
w/ getting a temporary account to submit changes and just having a
permement account to submit changes (other than the resource savings).
What repositories do this?