Re: [SVN-MIGRATION] Steps for the SVN migration

Hi,

Just wanted to jump in since we at PEAR have been using SVN for some
time now but only for code that didn't previously live in another repo
thus we haven't had the migration headache yet.

On Fri, Jul 25, 2008 at 11:18 PM, Lars Strojny <[email protected]> wrote:
> 1.) Do we want to use mod_dav_svn or svnserve, the subversion daemon?
>
> Pro:
>   * Allows to browse the repository with a normal webserver, very handy
>   * Allows to use mod_authz_svn for fine grained access (different
>     format from the current format, but easily to read)
>   * Is writable with normal WebDAV clients which might be a handy
>     feature for those, who do not want to bother with learning SVN
>     (those who do documentation translations, website updates, etc.)
>

We're using mod_authz_svn for our access control and it's working
pretty nicely - We actually maintain it in mysql and then we have a
mysql to svn authz file generator which I find quite handy, could
allow for some interesting ideas, like say ... handle the permissions
inside master.php.net, give certain users control over who gets karma
in X or Y group etc etc

> 2.) Single repository, multiple repositories. Do we want to use a single
> repository for all things PHP, including PEAR, PECL etc.?

I think each of the big projects should at least be their own repo,
simply sounds better from maintenance stand point and I also believe
it would be a heck of a lot easier to do different pre-commit hooks
for each project that way (or am I wrong on that one ?)

Anyway my 2 cents for now.

Regards
Helgi