Re: Enlighten about new SVN

On Fri, May 2, 2008 at 12:43 PM, Martin Jansen <martin@divbyzero.net> wrote: > > 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. Any RoadMap? I would prefer Trac or ViewVC interface. What about others? > > 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. Seems like smiles are not popular at all here. The main reason is security. Then scalability. > > 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. Of course not! Thanks for telling me. =) Did you thought about making http://pear.php.net to be Apache-based cluster with distributed DB-machines for each kind of serious application and distributed NFS for storage? Care to elaborate? > 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've seen some notes here about luring developers back to PEAR. These seemed somehow related to SVN. Have you tried to put a voting about what would people prefer to live and develop PEAR republic - i.e. "CVS, SVN or Do not care"? > 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. > To make a patch you need to make checkout, copy your patched directory tree over it and then build a diff. Since I was too lazy to install CVS tools right away I though I could wait another week to do this in SVN, but since you do not have any plans or goals or roadmaps on when it could be implemented, I doubt it will ever happen. I can help you with SVN setup if you can show where the main problem is. -- --anatoly t.