who's doing what? (was Re: [CAF] CAF development roadmap)

[Michael Graham]

> My rebuttal:
>
> 1. The one failing with SVN (for me) is that it still doesn't track merges
>    between branches.  This, just like CVS, makes having multiple development
>    codelines painful.

I think SVK and darcs both do this.  It's the "smart merge" (or "star
merge") thing.  But that may be a different feature I'm thinking of.  My
head goes all swimmy when I think about branch merging.

> 2. The perl5-porters think Perforce is okay.

I know, I hear great things about Perforce - and Richard likes it too.
I'm not criticizing it - I'm just saying that that the cgiapp crowd is
already split on SV[NK]/darcs, and I doubt they will be receptive to a
third option.  However that may not be relevent, because while we'd like
the core cgiapp developers to embrace/endorse our project, it's unlikely
that they will be submitting actual patches or code.

> 3. You have a volunteer, with the expertise to manage permissions properly,
>    at your disposal ;)

We have had an offer from Jason Crome to host a SVN repostitory (which
can be used as a backend for SVK).  Jason is hosting other cgiapp-
related projects.  I'm probably going to ask him to host my cgiapp
plugins.  

Also, Jesse Erlbaum donated a linux server for the use of cgiapp and
related projects.  Currently, it's just hosting the website and the wiki. 
But it may eventually host the version control repositories as well. 
Over the summer we were talking about integrated scm+rt+wiki solutions
like  Trac.  The hope is that we can eventually do this with SVN/Darcs +
RT + Kwiki.

> For example, I can make it so that only certain
>    people can write to the main codeline while side developers can pull in
>    changes from there and hack away.

Hey that's pretty cool!  I guess that's the centralized repository
approach to distributed version control.  In SVK or darcs, each
developer would have his own personal repository on his own machine
instead of a writable branch on the server.

> I'm happy with anything but I'd really feel more comfortable with a SCM/RCS
> system to save my work in.

Oh definitely - we need to get SCM working.  And realistically, I want
as little to do with its administration as possible.  So maybe that's an
argument for perforce.


Michael


---
Michael Graham <magog at the-wire.com>