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

Re: Design Questions

From: Jonathan S. Shapiro <shap_at_eros-os.org>
Date: 2000-07-29 01:06:01 CEST

> At a previous job we had contracted out all of our "learning products"
> and "localization". Due to a legacy architecture these files were
> spread all over the tree. We didnt want the contractors to have
> access to all the source code, but we did want them to use the
> version control system so their updates would appear in our daily
> builds...

Let me make sure that I understand this correctly. You wished to ensure that
it was completely impossible in principle for these contributors to even
*attempt* to compile their changes before checking them in and screwing up
the tree?

If I understand you correctly, this is one of those cases that I'm willing
not to support. People certainly won't always do the right thing, but
supporting a method to specifically *prevent* them from doing the right
thing seems like a bad idea.

If there is some other, conceptually sound reason, I'ld have no problem.

If by "we didn't want them to have access" you mean "we didn't want them to
have WRITE access", then the solution in DCMS would be to grant them
read-only access to the development branch. With read-only access, they can
create a writable branch of their own and then one of your team can
integrate their changes. This doesn't prevent them from modifying any file
they want, but it does allow you to check what was changed.

shap
Received on Sat Oct 21 14:36:06 2006

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