Re: Alphaworks for PEAR

Martin Jansen wrote:

On Thu Aug 14, 2003 at 03:5318PM +0200, Alexander Merz wrote:

Thinking about the PEAR_Error and Installer stuff Greg proposed this days, i had the idea to create a new directory in the PEAR-CVS: alphaworks. Maybe you know IBM's alphaworks website: http://alphaworks.ibm.com. This site is dedicated for projects based on new ideas and concepts, the projects there may be never released or going beyond an alpha state. In the alphaworks directory you can commit new features for the installer or for pear internals, like Gregs new error class or my pear_fanatic stuff.

I'm against this. Having something like that will end up in a garbage dump for all sorts of stuff that will never mature and will linger there forever.

That's a good point. Would it be possible to add this to the pear group's discretion? In other words, if code was only added if it directly relates to PEAR core, and only if PEAR group thinks it may be possibly merged to the core in the future. Also, I think it's reasonable to say that nothing older than 6 months should still be alpha, and should be deleted from the alpha repository (if it is not undergoing active development). This would make it easy to prevent the garbage dump syndrome. I, for instance, will simply move my error handling stuff into phpDOcumentor and other projects that need it, if PEAR decides ultimately against having it, or release a separate package if that is desired. I don't want my code to be alpha for more than a few weeks, if possible. :) I'd like to see things like work on the publicweb role, and work on automatic dependency resolution in some kind of public setting where others can try it out and comment before it is implemented in the core, perhaps the alphaworks isn't the solution, but currently we don't have an alternative. Greg