Extra Image Field Classes 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.
Comments
Comment #1
hongpong commentedHello all, I am willing to run the updates to get this to work on Drupal 9, and can thus be added as co-maintainer. It is used on a client site and I would like to just get it working as it should. (I have updated several other modules to D9)
Comment #2
hongpong commentedComment #3
gisleQuoting from the issue summary:
This project has opted into security coverage. Please confirm that you have this permission (aka. the vetted role).
Comment #4
avpadernoHongPong doesn't have the vetted role.
Comment #5
hongpong commentedIs this the correct info about the vetting process? Does it require another module to get reviewed and added first?
https://www.drupal.org/project/securitydrupalorg/issues/3243657
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
Comment #6
gisleYes. However, you should start out by reading: Apply for permission to opt into security advisory coverage.
Currently it does. The first issue you link to (#3243657: Proposal: make it easier for folks to know they're at a point to become vetted) suggest that this requirement is lifted and that some metrics identifying community members who've made signifcant contributions to other people's projects (e.g. through patches and merge requests) also shall get the role. It is a very new proposal, created just one week ago), and it looks like getting the software to collect and process these metrics is going to be a big job. Don't expect this to be adopted soon.
Comment #7
hongpong commentedThanks for the context gisle. I now have the vetted role and am ready to work on updating the module, following the security best practices. (I have been a registered contributor for 15 years but hadn't worked on this side of things before.)
Comment #8
avpadernoI added In HongPong as maintainer (user with all the permissions on the project).
Comment #9
avpaderno