info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Per-modules readers/writers ?


From: Todd Denniston
Subject: Re: Per-modules readers/writers ?
Date: Tue, 29 Oct 2002 08:17:15 -0500

Shankar Unni wrote:
> 
> Greg A. Woods wrote:
> 
> > Version control is a part of software configuration and
> > change management.  I thought that (what you said) is what
> > it (change management) was all about!  ;-)
> 
> Argh. I don't think I'm getting my point across, am I?
> 
> OK, forget I said "change management". The problem is that I (the
> repository administrator) often have *NO CONTROL* over how the system YP
> entries and groups are set up, because it's controlled and decided by
> some bureaucrats sitting 3000 miles away in an air-conditioned control
> room. Worse, it's often some gruesome hack on top of a Windows domain or
> something like that..
> 
> If this (Unix-level access control) is the only way available for me to
> control access to files, I am UNABLE to implement any access control at
> all.
> 
> Look, we all want to use CVS, because it's free. I agree, we're all
> weaselly cheapskates who want everything for nothing :-). 
<SNIP>
This is the point where you set down, add up what it will cost your company to
support your number of users by putting addons on a ''cheapskates'' version
control system to support its use in the companies IP policy setup.


Then add up what it will cost your company to support your number of users by
getting the hardware and software to setup your ''cheapskates'' version control
with the admin of the machine being the VC admin (not the bureaucrats 3K miles
away), so you can have your own groups file (or in addition to the YP groups). 
And yes you can setup a local box for this kind of thing, even against company
policy, but first you have to show a reasonable case for it being better for
the company to let you do it (or keep IT from finding out it is there), and
make sure it is always patched for all the latest worms/viri.



Then you set down again, add up what it will cost your company to support your
number of users by getting the hardware and software to setup "competitive"
thingys version control with the admin only having the control you know s/he
will have using a corporate system.

Like I think Greg was trying to point out, pick not the system with the lowest
price on the box, but the one which has the features which match what you NEED.


BTW by support, I mean not only initial setup, but maintenance of the VC system
and supporting hardware/database/OS.

-- 
______________________________________________________________________________
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power




reply via email to

[Prev in Thread] Current Thread [Next in Thread]