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

Re: Best practice, working copy and repository

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-10-02 00:44:33 CEST

On Oct 1, 2007, at 11:13, John Peacock wrote:

> On Oct 1, 2007, at 09:41, Turner, Alexis (GPG) wrote:
>> Please forgive the newbie question - I've just inherited a website
>> that uses Subversion which I have never used before. [snip]
>
> I suspect what you have is just a very poorly organized repository,
> with way too many projects lumped together [snip]
>
> It's not too late to reorganize your repository along more sane
> lines; it is merely a matter of a lot of 'svn mv' commands to move
> everything around [snip]

This isn't even a particularly Subversion-specific insight, but I
would rather suggest that if you have just inherited a project which
uses a tool which you've never used before, your first task should
not be to declare it to be poorly organized and restructure the whole
thing. Rather, you should work on understanding the project, and
understanding the tool that was used. Maybe you should give the
original developers and planners of the project the benefit of the
doubt, and assume that they did know what they were doing, and that
the current organization of the project may serve some purpose after
all. I suggest that only after you really understand the project and
the tool and have worked with both for some time should you
contemplate whether reorganization is necessary.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 2 00:47:03 2007

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.