The solution

In these 2 cases PEAR QA should step in and try to get in touch with the specific proposers. If the proposer is no more interessted in the proposal, PEAR QA should search for a new maintainer for the package or the proposal should be deleted.

For these steps the following time frames are proposed:

For proposals in stages "draft" and "proposal"

PEAR QA posts a reminder comment to the proposal after 1 week of inactivity.
If the proposer does not react within 2 weeks, the proposal gets deleted.

For proposals in stage "finished"

PEAR QA tries to contact the maintainer 4 weeks after the proposal is finished and no release has been throwen.
If the maintainer can not be contacted within 4 weeks, PEAR QA starts searching for a new maintainer.
If no new maintainer is found within 4 weeks, the proposal gets marked as orphan.

The above stated actions maybe automized inside PEARWeb in future, as far as possible.