Enlight about new SVN

Hello, folks I haven't used PEAR for a while, but have found some remnants of PEAR code on my HDD recently and decided to see what progress has been made by community so far. It was nice to see that after a year since initial proposal to switch to SVN there is a http://svn.pear.php.net/wsvn/PEARSVN However, there are not many packages included as it seems like it is more a probe than real installation. Therefore I would like to ask some questions that may affect the current state in the end. I wonder why http://svn.pear.php.net/wsvn/PEARSVN was used instead of more simple http://pear.php.net/svn/ URL? http://pear.php.net/svn/ URL need only one SSH certificate per domain, it is shorter and easy to remember along with http://pear.php.net/wiki/, http://pear.php.net/bugs/, http://pear.php.net/api/ etc. PEAR provides services for PHP developers I can't see why SVN is so different to be separated to fourth level domain. By the way, four level domains are ugly. =) If the four level domain is used to separate WEB and SVN server machines then it is a bad solution, because WEB interface for SVN will always be more effective when working directly with filesystem instead of accessing SVN via network protocols. By separating Web and SVN servers you lose many important integration options, such as ability to generate and apply patches via Web. About package placements in directory tree and the classical layout - ROOT/PackageName/branches - do you have any statistics on actual usage of branches in PEAR? How is the access configured - can I quickly open my own branch without asking package owners for permission to submit some proof-of-concepts for reference? I am asking this, because in the past I have to ascend up to top-manager level and compose several legal papers to gain write access just to reveal famous XML-RPC bug under my own name, which didn't happen anyway. Will there be a private areas for experimental code for people with SVN access? Step to switch to SVN is of course a big deal since its file-system based nature is much easier to explain than any other VCS. It also has a perfect and easy to read book. Since my pieces of code are mostly PEARDOC-related I would like to know how soon PEARDOC will be available for contributions in SVN repo? I know that now there is a PhD project in PHPDOC repository that contains more up-to-date code for Docbook-related tasks and if any university could make a real-world PhD out of it I could seriously consider to spend some time to port it to PEAR. But for now I just want to merge my changes into the trunk if there are any. With SVN there are more chances this could be already be done months ago when even with working CVS toolchain installed I didn't have enough time to prepare a checkin, because Internet access from this machine was through a proxy. After first look on new wiki and overall "redesign" it is good to see the progress in PEAR over two last years. What can I add - keep up the good work and make it not only seem to be less bureaucratic. Do not forget that only people who do the work provide real value, but this doesn't mean that their rules will make other people happy to contribute. -- WBR, anatoly