Re: Moving to a new PEAR website

On 05/03/11 16:23, Michael Gauthier wrote: >> For a start, can you please outline the process I should follow to move >> e.g. HTTP_Request2 to PEAR2? > Currently the process is: IMHO missing documentation is part of the problem. As maintainer of a small package my perspective is: "PEAR2 - that's sounds good. I'll try it when I have some time." --> Then I look it up in the PEAR Documentation and read "2007-12-24: This document cannot be considered complete". (http://pear.php.net/manual/en/pear2cs.php) --> conclusion "So it's still experimental, I'll check again next year." While I would gladly contribute the time to repackage my classes following a new coding standard, but I do not have the time to actively develop and discuss the new coding standard. So my wishes/suggestions are: 1. Put PEAR2 into the PEAR Developer Guide so one can easily look up how to write/migrate a PEAR2 package. 2. Set a date to migrate. Because moving one small package is insignificant ("I don't care"), but migrating the most popular classes and 50 small packages will make a difference ("Oh, everyone's moving, looks like I should update my stuff as well"). just my 2¢... -- Martin