Re: subversion module system question

On Wed, May 22, 2002 at 09:48:29AM -0600, Hamilton Link wrote:
>...
> Yes, thanks; I'm looking forward to pre-alpha. When you say track head
> you mean it can track the head of any branch, right? Probably a stupid

Yup. A branch is just another directory, much like the "trunk" is just
another directory. There is no distinction, as far as Subversion goes.
*Convention* (so far) states that we create /trunk, /tags, and /branches.
But any repository maintainer can set up any other structure they want.

[ for example, I think people maintaining multiple, disparate projects in
  the same repos will probably use a *very* different layout ]

> question, never mind. As far as converting the masses goes, any idea how
> many people are interested in SVN?

Everybody that I've ever talked to. I think that as soon as we release 1.0,
we'll see somewhere around 50% of the CVS users in the Open Source community
switching over (helped by things like the ASF, FreeBSD, SourceForge, GNU GCC
comptools, etc; all of them have shown interest in switching; maybe some
pieces of GNOME, too). I think that many of the 50% that haven't switched
will at least be experimenting with SVN within that first year.

Of course, all these numbers are pulled from thin air. But really... many
big repositories are considering the switch. Simply because SVN does so much
better with those big repositories.

I think the Open Source community will switch faster than businesses. Simply
because we're faster to adopt new technology and switch our processes as
needed; businesses usually have a bit of inertia...

> Will there eventually (and maybe I just haven't read enough of the
> Subversion docs) be functionality included in the server that quantifies
> (or even presents graphically) the amount of activity in a module?

If you can define how that is measured, then I could easily see
incorporating such a function into ViewSVN.

> what about built-in viewCVS-like module browsing?

Already being planned. In fact, we're going to extend ViewCVS itself to deal
with both CVS and SVN repositories.

[ need a new name, tho :-) ViewCVS just doesn't sound right for SVN :-) ]

> I guess I'll have to start building and playing with SVN so I can
> recommend it to all my friends.

You bet!

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org