Re: Moving to a new PEAR website

Hi Michael, On 03.05.2011 18:23, Michael Gauthier wrote:

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.

I think you approached the problem from the wrong direction. We need to promote PEAR2 and Pyrus, not pear2.php.net itself.

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.

At least there *is* a process... One can easily find a "Package Proposals" link and a relevant chapter in documentation.

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

What happens to http://pear2.php.net/PEAR2_HTTP_Request then?

[1] https://wiki.php.net/pear/rfc/pear2_class_naming [2] https://wiki.php.net/pear/rfc/pear2_exception_policy