Re: Enlighten about new SVN

On Sat, May 3, 2008 at 12:52 AM, Gregory Beaver <greg@chiaraquartet.net> wrote: > Martin Jansen wrote: > > techtonik wrote: > >> 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? > > > > Nope. > > These are all pretty buzzwords which I can translate for you into a > single fact: PEAR has no need for this kind of performance zooming, we > are using about 2% of the box (both CPU and disk space) that we have at > pear.php.net, and we also have mirrors at us.pear.php.net and > de.pear.php.net for installation. It is true that there are many buzzwords, but I it would be extremely interesting to see a working cluster created to simplify *.php.net projects maintenance. Hosting companies use common infrastructure to provide services to its users and here there also could be one centralized architecture where we can easily plug in new services on request. My last memories about *. php.net projects hold a vision of a pack of patches that are rather hard to push ahead due to the absence of common view. > > All of PEAR's web resources are generously donated by Pair Networks, > Bluga.net and Cweiske.de. > > >> 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"? > > > > Nope. > > The single most requested feature over the past 2 years has been for an > SVN repository, and since implementing, not one person has complained. But Marin said it is not implemented yet and because the work is in the process there is nothing to complain. > > >> 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. > > > > I don't think there are technical problems. I agree with your > > assumption that a transition from CVS to Subversion for peardoc isn't > > going to happen anytime soon. Get yourself a proper CVS setup and > > everything is fine. :) > > I wonder how you got a copy of the source of peardoc without using CVS? > This would be more onerous than the 2-liner: > > cvs -d :pserver:cvsread@cvs.php.net:/repository login > cvs -d :pserver:cvsread@cvs.php.net:/repository co peardoc > > and then edit peardoc source and the hard part: > > cvs diff -u > patch.txt > > The above commands assume unix. Windows is easy even if you don't have > tortoisecvs installed (again - tortoisecvs.org, click download, run > installer, reboot, right-click in explorer and do checkout, edit, then > right click and choose "make patch" and you're good to go) > > Is there a problem that needs solving? > Yes. First one is web proxy access. Second is that I am still convinced that you are losing contributors. The main problem is to prove that CVS is a history and there are no reasons to stick with it, because even the idea of votings is not supported as people afraid to give up their habits. =) I am willing to help solve problems with migration to SVN if anybody is interested. CVS can be syncronized and turned to r/o for historical reference. I propose the following migration scheme. If it could be started two SoC ago then we could see a working draft of online doc editor by now: [ ] place a page with link to core PEAR source repositories to pear.php.netbreadcrumb [ ] explain how the docs are build, where are site sources, where is repository for packages [ ] setup svn at pear.php.net/svn/ with ViewVC/WebSVN - pear.php.net/svn/.tags - pear.php.net/svn/.branches - pear.php.net/svn/package - pear.php.net/svn/package/Name/trunk - pear.php.net/svn/peardoc - pear.php.net/svn/pearweb [ ] setup CVS sync with Tailor [ ] plug in common .php.net authentication mechanizm [ ] design online peardoc editing tools with SVN bindings for PHP [ ] implement online source editing / patch creation tools with SVN bindings -- --anatoly t.