Re: Moving to a new PEAR website

On 2011-05-03 10:29, Alexey Borzov wrote:

Hi Michael, On 02.05.2011 2:49, Michael Gauthier wrote:

Further; not many pear1 packages have made the leap across - there's something missing (tools; knowledge; or as you suggest; exposure);

I'm not sure why more people have not moved packages over. Part of the problem is it requires a time investment many don't have, and requires breaking BC with existing stable packages (namespace support). For me, I'm just now starting to consider moving my maintained packages to pear2.

Where are current PEAR2 coding standards? Where is a guide for prospective PEAR2 developers? PEAR2 is esoteric, you should be already enlightened to contribute to it. Renaming pear2.php.net to pear.php.net won't fix absence of documentation, it will only make it more obvious. Yep, and that's terrible. One of the goals of PEAR2 is to make it easier for people to contribute. That goal has not been reached.

I feel like PEAR2 has a boot-strapping issue. No one contributes to PEAR2 infrastructure because no one uses PEAR2. No one uses PEAR2 because the infrastructure is not there. I thought moving the website would help this, but it could be the wrong decision. You also need to be enlightened to contribute to PEAR1. The process for contributing to PEAR1 has too much friction, and the existing docs are poorly written and difficult to find.

For a start, can you please outline the process I should follow to move e.g. HTTP_Request2 to PEAR2?

Currently the process is: 1. Use PEAR2 class/namespace rules. [1] 2. Use PEAR2 exception rules. [2] 3. Put code on github. 4. Ask someone on PEAR Group to add code to PEAR2 [1] https://wiki.php.net/pear/rfc/pear2_class_naming [2] https://wiki.php.net/pear/rfc/pear2_exception_policy