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

Re: rapidsvn feedback

From: Josef Wolf <jw_at_raven.inka.de>
Date: 2002-07-30 23:23:14 CEST

On Tue, Jul 30, 2002 at 09:24:59AM -0500, Karl Fogel wrote:
> Scott Lamb <slamb@slamb.org> writes:
> > Why?
> >
> > This information would be helpful. These are particularly important
> > when using SCM systems. Subversion now is getting relatively
> > experienced users who have used CVS, were dissatisfied, and are
> > willing to be on the bleeding edge to get something better. But
> > post-1.0, there will users who have never used another SCM system and
> > are not familiar with these ideas.
> >
> > The chapter could be called "Good SCM Practices" to clarify it is not
> > Subversion-specific.
> A brief rant:
> The challenge in writing documentation is deciding what not to
> include. Technical books typically run *over*, not under, their
> projected page count. If we're not careful, we'll have an enormous
> doorstop in which casual browsing is punished by acres of off-topic or
> redundant material. (Sound familiar? Sound like a lot of technical
> books you've seen? :-) ).

When I think about 10 years ago, I would be _glad_ if there were an
appendix "Good Praxices" in the CVS dokumentation. I had to learn it
the hard way because there was no such appendix. I think most of us
had to learn it the hard way, because there was no such appendix. Why
do you want to force people to learn the hard way? The problem is that
you can't easily correct most of those things reactive. If you don't
do it right from the start, the remainder of the (repo-)life will
claim for the sins of the early stages.

> Good SCM practices are completely independent of Subversion. You can
> use SVN without good practices. You can have good practices and yet
> not be using SVN.

Although this is true, I don't think it makes much sense to use svn
without good practices. Failing to use good practices will result in
failings to get benefits out of svn. Thinking this way, it makes
no sense to use svn without good practices.

But Anyway. Since it seems the svn core team don't like the "good
practices" appendix reside in the main handbook, maybe there could be
a consensus to create a separate good-practices-hadbook. While this
would be overkill(*), I think it would be better than having nothing...

(*) I don't think that this appendix would take much more than one or
    two single pages... Creating a separate document for a single page
    seems to be overkill to me... And it would make an additional
    hurdle for newbies, because they first have to _find_ this

-- Josef Wolf -- jw@raven.inka.de --
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 23:24:49 2002

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

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