Orphaned PEPr Proposals

Edited By

This document is based on the PEPr voting initiated by
PEAR's Tobias
Schlitt. The purpose is to define what to do with
orphaned PEPr proposals.

The problem

It happens more or less often that

PEPr proposals get stuck in a specific proposal phase,

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:

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 package has been released.

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.

Orphan marker

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

To the name of the proposal the following tag will be
added: [QA-ORPHAN].

To the description of the proposal the following text will
be added at the top: "This proposal has been marked orphan
by PEAR-QA on <DATE> because of the inactivity of the
proposer. This means, that the proposal is invalid from
this date on. If you have a similar proposal or want to
re-activate this proposal, feel free to create a new PEPr
proposal for it.".