Problem/Motivation

The Drupal community have a standard process for adopting abandoned modules, but it isn't mentioned in the Drupal Git Repository Usage Policy. While the Usage Policy does say

The repository maintainers can refuse or remove any content at their discretion and without prior notice to the affected party.

it does not indicate that if someone requests to become a comaintainer and hasn't heard back from the maintainer is two weeks that the d.o web team may forcefully grant someone else access to the project.

Proposed resolution

Add wording to the Drupal Git Repository Usage Policy page explaining the policy.

Remaining tasks

  • Decide on the exact wording to be added.
  • Update the Drupal Git Repository Usage Policy.
  • Notify everyone with git access of the change.

Comments

DamienMcKenna created an issue. See original summary.

jthorson’s picture

Assigned: Unassigned » jthorson
jthorson’s picture

Status: Active » Postponed

I intend to tackle this as a larger TWG documentation consolidation exercise circa DrupalCon Dublin.