Our company has started to look at CVS as an alternative to our current products. When I suggested using CVS I was told not having a lock file or method of knowing who was working on some code was going to be unmanageable. (and nearly beaten to death, by the developers)
Since Openbsd has the OpenCVS project, I thought you all might be the best people to ask about this. Is this really going to be an issue for a handful of developers?
Thanks in advance for your comments.
Roy Morris
Hi Roy,
Not that I know a lots about it, but looks to me looking from the outside that having locking on CVS would mean, only one would work on something and then reduce the collaborations between developers as well as slowing the developments and ideas are not share between multiple heads! (:>
Or to be a bit more crud, in business, may mean that if I make something bad, looking my section, mean other can't see my mistakes, so that I am never force to improve them, or correct them and this way,, I keep protecting my job and no talents, or lack of will not show up to often this way! (:>
May be I am all wrong, but locking would go in the oppose directions as to communicate and good design that comes from share ideas or process between multiple people where the best idea prevail oppose to mine because I lock the section of code.
Plus, improvement couldn't be done by others as it is lock!
My $0.02 worth from someone that most likely have no clue of what he is talking about, but only look at the logic of the process and the benefit of learning from others!
Or if I think I am God on earth and that I hold the truth, then yes I guess, may be, locking would be something I want as to not have anyone playing in my code! (:> But hey.... may be many thinks they are God and want locking in their tree! (:>
Just an outside point of view.
Daniel
