Content connected has been automatically opened to new maintainer applications, as it has releases for Drupal 8 which will be marked unsupported on 2 Nov, 2021, but no release yet for Drupal 9. Your Drupal 7 releases will not be affected.
This is an adaptation of our existing process for transferring project maintainership.
After the standard 14-day waiting period from this issue being opened, and if an existing maintainer has not closed it, this project becomes eligible for new maintainers. Those new maintainers will not need to wait for existing maintainer approval.
Next steps:
- An existing maintainer may close this issue and opt out of this accelerated process.
- A prospective new maintainer can take this issue after the 14 day window has elapsed and take the following steps to be added as a maintainer:
- Comment here explaining why you would like to maintain the module.
- If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.
- If an existing maintainer has not commented, move the issue to the Drupal.org Project Ownership queue, by editing the “Project” field on this issue.
- The Drupal.org site moderators will review the issue, and if it meets the requirements can grant you maintainer access.
Comments
Comment #2
javivf commentedWe (as Digitalist) would like to maintain this module because we are currently using it and we want to contribute back to the community.
Comment #3
javivf commentedComment #4
avpadernoThe project is covered by the security advisory policy. Site moderators won't add as co-maintainers/maintainers users without the vetted role.
Comment #5
avpadernoComment #6
bletch commentedI am happy to take over maintenance of this as we appear to be the only org using it. I have security coverage opt-in.
Comment #7
bletch commentedComment #8
avpadernoI added bletch as maintainer, since she can opt projects into security advisory policy.
Comment #9
avpadernoComment #10
bletch commentedThx!