PEPR for PEAR2

What would we need to change about PEPR to make it be "PEPR for PEAR2"? http://pear.php.net/manual/en/developers-newmaint.php Revamp of the new maintainers guide to reflect pear2 standards; expectations; building / testing your package with pyrus. http://pear.php.net/pepr/pepr-proposal-edit.php Revamp of text to talk about PEAR2; explain we aren't taking any new submissions over here; pear coding standards link to be pear2 Overall process: * People don't go through all of the stages particularly well - http://pear.php.net/pepr/pepr-proposal-show.php?id=649 or the many unfinished proposals * The +1 / -1 works well. * Admin - setting up a new package (current pearweb), granting svn karma; welcoming the successful developer etc - the knowledge on this is handed down from person to person; and isn't documented overly well. * We should find other frameworks and communities; and link to their "submit package" areas too - http://framework.zend.com/community/contribute or http://trac.symfony-project.org/wiki/HowToContributeToSymfony for instance. General prettiness would be a nice to have; but is perhaps something we can defer until later - rewriting or migrating the functionality into pear2.php.net or a (more) standalone process. What else?