Description: ------------ The PEAR manual should clearify the official (true one) approach to follow proposal-wise or at least state that both ways are viable - statement consistency in both of the following chapters: http://pear.php.net/manual/en/newmaint.proposal.step2.php Chapter 10. The formal proposal process - Step 2: Initiating a discussion Before starting the proposal process in PEPr, a thread should be started for each new package on the developers mailing list. This intermediate step is preferred for the sake of convenience, because it is easier and more comfortable for us to hit a single key in our mail client to join a discussion than to open a browser window and look up the right page on the website... is somehow in contradiction with http://pear.php.net/manual/en/developers.contributing.howto.php Chapter 13. Contributing your own code. How to contribute code in practice - 2. Announcing to the PEAR developers The second step while contributing is to announce your package in PEPr. Usually this announcement will spawn some discussion. After one week you may call for votes with PEPr and the developers will then start to vote for or against your proposal. (You are of course urged to join the upcoming discussion.) Announcing a package does of course not mean that it is already accepted! That will still take some time and likely some more efforts from your side... Which is the correct way to go: PEAR-Dev and/or PEPr?