|» Metadata||» Status|
It happens more or less often, that
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"
For proposals in stage "finished"
The above stated actions maybe automized inside PEARWeb in future, as far as possible.
Finished proposals should not be deleted, but marked as orphan. This marker should have the following content:
To get this process running, an initial cleanup is required. The procedure is only run once, when this proposal gets accepted. This cleanup should have the following steps:
Proposals in stages "proposal" and "draft"
PEAR QA will post a reminder comment to every proposal which shows no action since 4 weeks. If the proposer is not reachable within 1 week, the proposal is deleted.
Proposals in stage "finished"
PEAR QA will try to get in touch with the proposers of every proposal which is older than 4 weeks and for which no package has been registerd, yet. If the proposer is not reachable within 2 weeks, the proposal is marked as orphan.
|» Dependencies||» Links|
|» Timeline||» Changelog|