Re: future of PEAR (was [PEAR-DEV] [Call For Votes] PHP::Fork)

On Tue, 2003-11-11 at 06:03, Greg Beaver wrote: > -- cross-package API. All packages within a category should share a > common API, so that it is relatively simple to switch from similar > package to package (DB_NestedSet to XML_Tree's DB driver, for instance). > This would also solve the issue of redundancy. If a better way to do > something comes along (Cache_Lite vs. Cache), a common API will allow > people to switch from one to the other much more seamlessly than now. I think this should depend on the categorie and the maintainers. If there are several packages with nearly same function (see: Template) I think a factory pattern could better solve the way, but for many categories common APIs could not work. What we better could do would be to write down naming conventions for commonly used methods (as fetch(), toFile(), render()) to get a smoother API community. I'd like that. > -- political issues in the structure of maintainers and of PEAR group. > PEAR group has too much responsibility, and no time to enforce it. > packages with critical bugs remain untouched because there is no easily > defined way to handle unmaintained packages, etc. etc. It would be nice > if PEAR group was somehow accountable to the rest of PEAR as well. A > study of functional political entities in the programming world and in > the real world would be informative.