Offering to maintain RabbitMQ

We at Yle are using this module and wish to continue so. It fulfils our needs and has worked great so far. However this issue about the maintenance is a bit worrying and there are other issues that are pending for reviews while the activity around the module seems quite low. Is there something that we can do to help?

Hello Jonhai,

I'm not the owner of the project, although I contributed a good deal to it, but FWIW I don't have any objection, especially give that the D8 port I created was for a national broadcasting company already :-) I have just a question: I do not see any commit under your name; maybe it would be better for you to start by contributing code or reviews on existing pending issues before taking the load of maintaining it yourself ? You don't need any specific privilege for that.

Thanks fgm, contributing on the existing issues sounds like a good starting point. We'll look into that.

Expanding on @fgm's comment.

You do not need to have a history of using the module or code commits with the module to adopt it. Even a less experienced maintainer is presumed to be better than no maintainer. Knowing what the module does and how it works however will help you make a more informed decision before offering.

However this module is enrolled in Security Advisory Coverage, that means the user who offers to maintain as part of this issue MUST have the vetted role. Just working on issues in the queue will not allow you to obtain that status if you do not already have it. Unfortunately who has this role is not visible to the Drupal community at large, however the fact your account shows no commits to any projects I'm guessing you do not @jonhai, is that guess accurate? Does anyone on the YLE team have the vetted role and would they be willing to take on the module?

Not every maintainer needs to have the vetted role, however the individual that wants to apply must and once approved can add other maintainers without the role.

jonhai doesn't have the vetted role, which means Drupal.org site moderators won't add him as maintainer.

This automatic issue should not have been created, though: There is a project release that is compatible with Drupal 9. Probably the issue has been created because that release (a development snapshot) is not visible in the project page.

@apaderno

I was considering offering if @jonhai responded that no one at YLE has vetted and wants to take it on (first right of refusal to their team as they may be using it more in depth than I am at the moment.)

Do we need to close this and go through the standard unsupported process if we wanted to proceed?

@cmlara @apaderno

Unfortunately we don't have anyone at Yle with the vetted role, but we'll try to help with this module through code and reviews.

@cmlara SInce this automatic issue has been created, we will use it. I take the requirements to create it are not as simple as I thought. If you want to offer as maintainer, move this issue in the Drupal.org project ownership queue.

Because @jonhai has responded that no one at YLE currently has the vetted role to be able to move this forward and @apaderno has confirmed we can still use this issue.

I would like to volunteer to be added as a maintainer for the module. I am still in the early stages of a project that requires the ability to integrate with RabbitMQ in D9 and would like to see the module make it to a stable release with community involvement and without fear of the possibility of security vulnerability triggering an unsupported SA in the future.

I have the security coverage opt-in permission.

@jonhai Assistance with code and reviews in the issue queue would be greatly appreciated, those are the some of the most important parts of the process.

I added cmlara as maintainer, since he has the required role.

Thank you @apaderno!