Mirador 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.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Scanning report.png | 100.15 KB | mitthukumawat |
| #2 | 3233710.patch | 355 bytes | mitthukumawat |
Comments
Comment #2
mitthukumawat commentedAttaching patch for compatibility of Drupal 9 for this module.
Comment #3
mitthukumawat commentedComment #4
abhinand gokhala k commentedHi @mitthu, Could you please attach the scanning report for the compatibility of Drupal 9.
Comment #5
mmjvb commentedSuggest to continue https://www.drupal.org/project/mirador/issues/3148148 for D9 version.
This issue is about transferring ownership. Sounds like it should be closed as Works as Designed assuming no desire to transfer ownership.
Comment #6
mitthukumawat commentedAttaching the screenshot of scanning report for the compatibility.
Comment #7
Ankit@gvp commentedwe added patch as per #2
it shows following
'Problem 1
- drupal/mirador dev-1.x requires drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but the package is fixed to 9.3.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/mirador 1.x-dev is an alias of drupal/mirador dev-1.x and thus requires it to be installed too.
- Root composer.json requires drupal/mirador 1.x-dev@dev -> satisfiable by drupal/mirador[1.x-dev (alias of dev-1.x)].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.'
Comment #8
mmjvb commentedPlease turn to the other issue for D9 compatibility. The patch needs to be committed by maintainer to be of effect when using Composer. Which is why this issue exists, looking for maintainers to actually do what is requested. It appeared current maintainer was interested to do some work. So far, it wasn't done. So, interested maintainers can respond here to take over this project and make it available for D9 by working on the appropriate issues and commit and create a release.
As the patch is on meta data, it needs to be committed to have an effect to Composer. The alternative is to create your own package and provide a repo to that.
Set back to active as no maintainers volunteered to take this project on!
Comment #9
sanduhrsHello :)
applying as a new maintainer for Mirador
https://www.drupal.org/project/mirador
> 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.
I am planning to use this module in a D9/D10 project.
>If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.
I have previously received security coverage opt-in permission
Please consider transferring ownership to me.
Comment #10
avpadernoI added sanduhrs as maintainer, since he can opt projects into security advisory coverage.