Search API Elasticsearch Attachments has been automatically opened to new maintainer applications, as it will otherwise become unsupported with the end of life of Drupal 8 on 2 Nov, 2021.
This is an adaptation of our existing process for transferring project maintainership.
After the standard 14-day waiting period from this issue being opened, if an existing maintainer has not closed it, this project is eligible for new maintainers, without necessarily waiting for existing maintainers’ 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.
Issue fork search_api_elasticsearch_attachments-3234555
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
jlstreckerThis module has an RTBC issue for Drupal 9 support. If we could get that issue merged, it would free users from having to create their own private forks or other workarounds to use the module with Drupal 9 (edit: specifically, installing with Composer).
Additionally, this module has an effectively RTBC issue for Elasticsearch 7 support. This would make the module compatible with the current version of the Elasticsearch Connector module and an Elasticsearch version that has not yet reached its end of life.
dakku, would you be able to merge those in the near future?
If not, what would be the best way forward?
Although I don't have the time or Elasticsearch experience to take responsibility for this module for the long term, I would be happy to act as maintainer temporarily to get the above issues merged, if that would help.
Comment #4
jlstreckerComment #5
avpadernoThe project is covered by the security advisory policy. Only users who can opt into security advisory coverage will be added as maintainers.
I am moving the issue back to the project queue, to allow users with the right role to be added as maintainers.
Comment #6
olarin commentedI believe I do have the necessary role to opt into security advisory coverage, and I'm willing to make the same offer as jlstrecker.
Comment #7
avpadernoI added Olarin as maintainer, since he has the required role.
Comment #8
avpaderno