Document process for abandoned Extensions, with either someone taking over the extension maintainer role or de-listing the extension
Created by: jusfreeman
Document process for abandoned Extensions, with either someone taking over the extension maintainer role or de-listing the extension.
This should also include a process for reporting an abandoned extension and the process to be followed for either de-listing or transferring maintainers.
The documentation on Extension Lifecycle is deficient, there is no recognition of an extension being "abandoned" as is this case with the ChrisChinchilla/CiviCRM-eWay-recurring-payment-processor, see https://github.com/ChrisChinchilla/CiviCRM-eWay-recurring-payment-processor/issues/59
Abandoned software is a common occurrence, as you will have no doubt seen in other open source communities such as Drupal and WordPress.
Relates to this discussion, extensions/extension-review-requests#11 (closed)
Agileware Ref: CIVICRM-1375