Offering to maintain Image Widget Crop

Here is the message that have been sent to the 3 "human" maintainers of the Image Widget Crop module :

Hi,

We are using the Image Widget Crop module on some web sites.

We need to be able to use this module on some new Drupal 11 web sites.

I volunteer to maintain the module and pledge to do a Drupal 11 release as
soon as possible.

You can check my profile with all the modules I am currently
maintaining here :

https://www.drupal.org/u/mably →

Here is the issue relative to my maintainership offer:

https://www.drupal.org/project/image_widget_crop/issues/3480976 💬 Offering to maintain Image Widget Crop Needs review

Regards.

Frank

I am going to contact three maintainers, who at least logged it once in the past 12 months.

I contacted woprrr, and this is the message I sent.

Hello Alexandre,

I am contacting you because Frank ( https://www.drupal.org/u/mably → ) offered to become maintainer for Image Widget Crop ( https://www.drupal.org/project/image_widget_crop → ), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3480976 💬 Offering to maintain Image Widget Crop Needs review about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Frank will be probably made maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving Frank all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3480976 💬 Offering to maintain Image Widget Crop Needs review .

I am contacting all the people who can administer co-maintainers/maintainers for the project.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

I am still contacting the project maintainers.

I contacted all the project maintainers.

The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

Ok, thanks Alberto!

Hi! I am one of the maintainers, but have not been involved with IWC for a while. Original author of the module is @woprrr and @phenaproxima seems to be the most active lately. I would prefer if they would weigh in. With that said, I am OK with granting @mably committ access and I can do so if they don't respond.

I'd give them some more time. Please get back to me if they don't (email me as I am not monitoring this issue).

I have contacted @woprrr already some days ago offering to co-maintain and help getting a final Drupal 11 release. As I know very well from own experience as a maintainer of multiple contrib modules, maintainers possibly have a lot to consider and to manage on a time table and it is fully understandable that they cannot repond immediately. So let's be patient please and wait some days if he responds. In case my invitation to help is welcome, I will help to get a Drupal 11 release asap. To request a take over feel a little bit harsh to me for that situation.

That was the message I send to @woprrr using the contact form on D.O.

Hi @woprrr,

How are you? I hope you are well in these strange times. Thanks for all your
awesome contributions to the Drupal community! You rock! Since the company I
chair as CEO (MAROQQO digital media) and my team has agreed to support
contributions to this project and to move on with some feature additions and
patches in the issue queue to make this project Drupal 11 ready and prepare
it before Drupal 12 lands, I would like to invite you to add me to the
co-maintainer tab for this project to come over long holding waiting times or
the need to contact maintainers each time for another review or new patches
or commits on RTBCs.

My consideration is based on the assumption that you and other maintainers of
the project do may not have enough time to keep track on this at the moment
(which is absolutely understandable) and I would like to help out for your
project to move on. So I hope this message does not reach you mistakenly. If
you plan to put more time into the project soon, consider/regard my request
as settled (obsolete).

Have a nice Week!
@dqd (Sebastián)

Quick news: I've been added as co-maintainer at this moment. So things move on. I will help to get a final Drupal 11 compatible release in the next days and the work on long holding issues and RTBCs will go on to make the project ready for the further future. So things are moving on now. +1 I hope it helps.

@dqd Great news!

@mably: I hope it helps to move on. Do you feel your worries settled for now so that we can close this issue at this moment? From my understanding regarding the situation it is a little bit too early to rush fences here. I think it would be better to cooperate with active maintainers and communicate possible existing road maps and contribute to them before entering the ship.

As you want. If you need help, I'm available.

Thanks for coming back on this @mably. Your efforts and contribution is very much appreaciated! If it is OK for you and the moderators of this issue section, I would recommend to close this issue and wait if upcoming progress on the project is satisfying.

In case if progress stalls and requires action, another request of you, or me or anyone else could be considered. Until then I would recommend to leave the project in the hands of the active maintainers and wait how the responsivness goes on. In the moment I got very responsive support of active maintainers how also invited me to contact them for any help.

Automatically closed - issue fixed for 2 weeks with no activity.