Orphaned PEPr Proposals

JavaScript Editor Javascript validator     Web page editor 



Orphaned PEPr Proposals

The problem

It happens more or less often that

  1. PEPr proposals get stuck in a specific proposal phase,

  2. PEPr proposals get accepted, but no package is registered / released.

The solution

In these two cases PEAR QA should step in and try to get in touch with the specific proposers. If the proposer is no longer interested 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:

Orphan marker

Finished proposals should not be deleted, but marked as orphan. This marker should have the following content:




JavaScript Editor Javascript validator     Web page editor