Re: Discussion of SCM_SVN Proposal

From: Chuck Hagenbuch <chuck@horde.org> > > I don't think the category name should be required as a class prefix. > It'd just > be unnecessary overhead. Interesting point -- I'd rather have it be "SVN" that lives within Tools myself, but I'm trying to comply with the PEAR manual on this issue. See: PEAR Manual > How to contribute code in practice > Finding an appropriate package name http://pear.php.net/manual/en/developers.contributing.howto.php > As opposed to rewriting VC_svn to use SCM_SVN and adding another layer for > anyone who wants to use Chora with Subversion? That sounds like overhead to > me... Overhead for the Chora application, perhaps -- but not for the maintenance/creation of a low level API. > And rewrite Chora from scratch to use it, ditching all of our experience and > bugfixes in the process? In my experience, writing something from scratch is > rarely more effective than refactoring existing code if the goal remains the > same. Chora is under no obligation to use my package, whether or not it lives in PEAR or doesn't. The Horde guys will have to make that decision on their own, just like any developer of a database-driven application decides among using native PHP extensions, a third-party package like ADOdb, PEAR DB or PEAR MDB, or the third option that some people choose of rolling their own mini-abstraction layer. To each his own -- what Horde does or does not adopt for the Chora application is up to them. I wrote my package because I need low level version control API capability in a couple of apps I'm working on. I submitted SCM_SVN to PEAR because I like the code that lives in PEAR, for the most part, and the PEAR project has no version control package (for Subversion or anything else). The PEAR project _still_ has no version control package, so I think the grounds for my proposal to PEAR -- "Hey, there's not a Subversion package in PEAR! I bet PEAR could benefit from such a package! I'll write a Subversion package for PEAR!" -- are still solid. It was not my intention to stir up some hornet's nest, or to propose something that would be perceived by anyone as a competitor to Horde. I've proposed a low level API for the PEAR project -- I'm just trying to fill a small hole that I saw (and still see) in PEAR's otherwise robust offerings. -Clay -- Killersoft.com