On Fri, Jul 28, 2000 at 07:06:01PM -0400, Jonathan S. Shapiro wrote:
> > 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?
Believe it or not that was the case. They didnt have access to the other
files, but they did have access to the resource files (it was a win32
environment) they were chaning and that allowed them to check window sizing
etc.
> 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.
I definitely can understand not wanting to support this as it was a very
unusual case. But I think defining right/wrong is inappropriate as it
is situation dependent. Ill skip going into all the IP issues that were
involved with this particular situation.
-----------------------------------------------------------------------
John Cavanaugh Agilent Technologies
R&D Program Manager 1400 Fountaingrove Pkwy
CAD Data Store Santa Rosa, CA 95403-1799
Email: cavanaug@soco.agilent.com Phone: 707-577-4780
707-577-3948 (Fax)
-----------------------------------------------------------------------
The main thing people really regret
are the risks they didn't take......
-- Unknown
-----------------------------------------------------------------------
Received on Sat Oct 21 14:36:06 2006