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

Re: Subversion for VSS users

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-06-08 14:54:36 CEST

On 6/8/06, Kenneth Porter <shiva@sewingwitch.com> wrote:
> --On Thursday, June 08, 2006 1:38 PM +0200 Markus KARG
> <markus.karg@quipsy.de> wrote:
> > I also was a member of the point-and-click crowed using VSS 6, but the
> > SVN book made me a believer. ;-) Read the book. It's the best way to
> > learn SVN. Even for dummies like me. ;-)
> I agree. It's very well-written. But when getting people to convert to a
> new system they often look for an excuse to fail, and having to read much
> to "get off the ground" can be a barrier to acceptance. It's not that the
> material isn't in the book. It's that the packaging suggests that one needs
> to read the whole thing before one can start. So abstracting out enough to
> do basic operations, a "quick start guide" if you will, would be a useful
> thing. Even something like you'd find in a magazine review would be fine.
> Just something that let's the PHB's get their head around it without having
> to read the full treatment. (I refuse to stoop to asking for a PowerPoint,
> though! Blech!)

So give them the first 2 chapters of, say, William Nagel's /Subversion
Version Control/ (23 pages) or the first 2 of Mike Mason's /Pragmatic
Version Control Using Subversion/ (26 pages).

A side benefit of doing this is you're demonstrating that the software
has real, professionally-published paper documentation, which may help
give it some extra credibility in management's eyes.

Could the "official" book use a better PHB/executive summary chapter
to lead in? Looking purely at the TOC, probably.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 8 14:56:22 2006

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.