Re: A virtual file system

Quoting Alan Knowles <alan@akbkhome.com>: > Not that I wouldnt love a Horde acount :), but one of the benifits of > using pear's cvs, is that when there is something 'obviously wrong' with > a pear package - eg. A bug... anyone with a pear account can fix it - by > commiting it. (and get shouted at if they break something :).. And the same goes for, and frequently happens with, code in our CVS tree. Also, for the record, PEAR's coding standards were adapted from Horde's, and we don't fight about them anymore, so consistency and checks for E_ALL errors are at least as good in our code as in PEAR's... > It makes life alot easier for package mainterers - if someone suggets an > extra method to their package (and the owner likes it), then if the > proposer has a pear account, they can go ahead and commit it, saving the > maintener some time.. We routinely give CVS accounts to anyone who shows an interest in submitting more than one patch. We also have a large installed base of applications that rely on our components such as VFS; I'm willing to put in the time taking care of patches in exchange for a slightly less volatile codebase. > It also makes browsing the source code easier to find (as that is often > the best way to review a package before using it).. http://cvs.horde.org/ and http://dev.horde.org/ (some of which is auto-generated every night). It's not so hard to find - and if this is really a concern, then the PEAR website folks will make linking these kind of resources from pear.php.net easy. -chuck -- Charles Hagenbuch, <chuck@horde.org> "After a few minutes the most aromatic and nice smelling Italian coffee will come out of the exhaustpipe." - Our stove-top espresso pot