Sometimes a package is left without care for a long time. It becomes lonely and full of bugs. This is a very sad situation and somebody needs to step up to remedy it.
The following are considered orphaned packages:
A QA core-team member tries to contact the current maintainers and developers (cc'ing the QA list) asking about an update about their work on the package.
A package lead answers:
A message will be sent to pear-dev asking for volunteers.
If you are willing to take over a package you must notify the QA list and state who you are and why you want to take over.
If the QA team feels the person who stepped up is appropriate and capable, the team will make this person a new maintainer. In case several persons step up a case by case study will be carried out to assign new maintainer-ship.
A QA core team member will mark the package as orphaned.
If a package is orphaned, a warning and a call for maintainers will be displayed on the main package page.
Descriptions of terms used on this page
|QA team||Refers to the whole QA team (core and mailing list members)|
|QA core||Refers to the 6 elected QA team members|