bringing version control into the company [semi-OT]

This is more of a general version control question...hope you don't mind.

My company, in a nutshell, creates and manages webstores for other
companies. We have 3 developers and 3 designers, and we manage about 40
stores. Now all the developers want to bring version control into the
fold and the boss is responsive to the idea but he wants to try to "disrupt"
the designers lives as little as possible. I, being the one whose really
acting as the champion for version control, have been nominated to talk to
the designers about their concerns and fears, and try to reach a happy
middle ground. Unfortunately, their concerns are huge obstacles:

* "I don't want to do anything differently than I do now"
* "I don't want to use another program for managing the files"
* "I don't want to work on the files locally, I want to work on the DEV
server directly"
* "Why do I have to make a log file for EVERY change?"

I was curious if others have run into similar situations when trying to
bring version control into your organization, and how did you overcome them?

-Christian

--
God put me on earth to accomplish a certain number of things.
Right now I am so far behind I will never die.
-Bill Waterson, Calvin and Hobbes 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org