The main problem with this RFC is that it covers too much ground and some of the parts are too vague.
*Membership and related*
This should be a separate RFC.
Right now if the package does not have docs and/or a test suite only its author can decide what is a bug and what is the expected behaviour. The proposed solution --- electing the bugs by popular vote is not better.
Besides, fixing the bugs without running tests may obviously cause more bugs.
I don't see any intentions from PEAR QA advocates to create tests for packages, so am 99% sure that we'll soon see much problems from half-baked "fixes".
Should have a separate RFC for these.
*Deleting Package releases*
Where is the list of reasons?
*Approving first stable release*
Where are the criteria for the stable release?