Re: Enlight about new SVN

On Fri May 02, 2008 at 09:0735AM +0000, techtonik wrote: > 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 Please note that the Subversion setup is far from being finished. Things will likely change in the future. > I wonder why http://svn.pear.php.net/wsvn/PEARSVN was used > instead of more > simple http://pear.php.net/svn/ URL? Because the Subversion server is on a different box than the web site. > 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/, The wiki is on another box as well. > 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. Huh? The web interface will in fact live on the same box as the Subversion server. This happens to be svn.pear.php.net for the reason I outlined above. No big deal. If you don't like long domain names, this really is your problem, not ours. Sorry. > By separating Web and SVN servers you lose many important integration options, > such as ability to generate and apply patches via Web. Ever heard of communication via networks? That's how the Internet works. > 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? There is no migration plan of any sorts for these things. As I wrote above, the Subversion setup is work-in-progress. > 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. You can always send your patches to pear-doc@lists.php.net. I'm sure someone will take care of them. Martin