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

[OT] Call for closed-source case studies of Subversion "switchers"

From: Brian W. Fitzpatrick <fitz_at_red-bean.com>
Date: 2005-07-28 23:06:36 CEST

Sorry for the noise folks, but I'm doing a presentation at OSCON
(Portland, OR) next week and I'm going to be presenting some case
studies of projects that have switched to Subversion. In particular,
I'll be touching on the social elements of changing to a new tool
(Session abstract here http://conferences.oreillynet.com/cs/os2005/

I've already got some big open source switchers to talk about (KDE,
Mono, The Apache Software Foundation, and GCC), but would really like
to have a few case studies for people who have switched to Subversion
on an internal corporate project of more than 25 developers.

If you're willing to be one of these case studies and don't mind me
talking about your company (I'll be glad to keep the name anonymous
at your request), please respond to the following questions in this
mail (offlist, *please*).

Thanks all and pardon the noise,


The case study questions:

0. What version control system were you using before switching to

1. What did you do to get your developers to buy in to the svn switch?

2. Were there big resistors? How did you deal with it?

3. Did you do a pilot? A test conversion and let folks use it? etc.

4. Did you consider other vc systems?

5. Did you find that svn was missing anything and that you had to
    compromise to gain other strengths of svn? (ala slow

6. How many read/write users do you have? How many read-only users?

7. Did you have any problems making the switch?

8. Is there anything that you'd do differently if you could do it all
over again?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 28 23:08:33 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.