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:
he states that he has no interest in the package anymore,
he allows QA team to take the necessary steps
he states that he still intends to work on the package, but
is busy at that point. Either a timeframe will then be
decided upon by the lead and QA during which some activity
must occur (i.e. I'm going to be busy the rest of this
month but I'll get back to it on the 3rd of next month) OR
a second lead developer will be sought to continue
development
he states that he still intends to work on the package, but is
busy at that point. Either a timeframe will then be decided
upon by the lead and QA during which some activity must occur
(i.e. I'm going to be busy the rest of this month but I'll get
back to it on the 3rd of next month) OR a second lead developer
will be sought to continue development
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.