Hmm. Maybe we should use Subversion? We could certainly not worry about directory organization in that case. We'd lose CVS history, though, since we can't blend multiple CVS repositories over time. i.e. we could use cvs2svn for an initial set, but future additions would lose history since we couldn't "blend" them into an existing repos.
I would personally be a strong +1 for using Subversion for serf. I think Subversion is ready for a trial run here within the ASF.
That said, I'm going to stay the heck out of this policy debate. I want to see serf move to commons, but I'm not going to waste my breath arguing over it. I've stated my position, and I'd rather spend my time improving the code. -- justin
